| author | Norbert Thiebaud <nthiebaud@gmail.com> | 2012-05-04 05:21:01 (GMT) |
|---|---|---|
| committer | Norbert Thiebaud <nthiebaud@gmail.com> | 2012-05-04 05:22:41 (GMT) |
| commit | 6670aa7193c3a629e2f1477fe56e9b4b2dfd5ab6 (patch) (side-by-side diff) | |
| tree | 1a79fd7036f40ca00a02ee79a1d57251b88dd6ed /bin/tinbuild | |
| parent | 3e5b5c06343ebbf80a4a9952ff52a0031d54898e (diff) | |
| download | buildbot-master.zip buildbot-master.tar.gz | |
This presume that .ssh/config define 'gerrit' properly so
that ssh gerrit point to gerrit with the right user, key and port
usage: in a core repo, with a profile who's autogen.lastrun limit the build
to the core repo (no help/no dict/no binfilter and no i10n)
tinbuild2 -p gerrit -g refs/changes/x/y/z (as provided in the gerrit gui)
this will essentialy check out that change in a headless branch, build it
like for a 'prime build' and notify gerrit of the result via the
gerrit review command line
TODO: notify at the bebeggin too to announce the start of the test-build
This will eventually be able to be controled via a daemon that will
monitor which patcheset need building and submit such tinbuild2 commands
as needed
0 files changed, 0 insertions, 0 deletions
