Sorry, but this is only available to Google employees at the moment. Make sure you've joined the chromeos-team group.
Remote trybots allow you to perform a trybot run of multiple configs/boards in parallel on remote servers. A trybot allows you to emulate a buildbot run with a set of your changes. The changes are patched to tip of tree (TOT). It supports running of Paladin, incremental, and full buildbot configurations.
It supports patching of both gerrit CL's and changes you've committed locally but haven't uploaded.
The remote trybot waterfall is located at https://uberchromegw.corp.google.com/i/chromiumos.tryserver.
Run the following from within your repo source checkout:
Substitute [config [config...]] with a space-separated list of your desired configs. Prepend a '*' to the CL ID to indicate it's an internal CL. The CL ID can be a Gerrit Change-ID or a change number.
This runs a tryjob for the alex-paladin and x86-alex-release configs in parallel. It patches in two CL's: 1) an external CL using a Gerrit change number 2) an internal CL using a Gerrit change number. In case a CL has several patches associated with it, the latest patch is used.
Note that specifying the same configuration multiple times is permitted. This will cause multiple instances of the same config to be tried in parallel.
For example, this patches CL 356903002 into Chrome's /src directory and tries one bot:
This patches 11659002 into chromium/src/tools/gyp and tries two bots:
If you are asked for a username and password check your ~/.netrc. If you don't see entries for chromium.googlesource.com you need to generate a new password.
Internal rietveld CLs are not yet supported.
3c. To patch in a local patch, run:
Specify the name of the project (not the path, look for projectname in .git/config) and optionally the project branch. If no branch is specified the current branch of the project will be used.
This patches in any commits in project chromiumos/chromite's current branch and on branch 'my_branch' in project chromiumos/overlays/chromiumos-overlay.
3d. To test patches for a release branch (i.e., R20, R21) use the --branch (-b) option with -g:
git checkout cros/master
Local patches (-p) to branches are not yet supported.
3e. To create an official release using tryjobs from a branch:
In the case where you would like all boards built (*-release[-group]), just list each try config separated by spaces.
Now we've landed more changes on stabilize-4731.62.B in order to fix something for parrot:
wait until the "ManifestVersionedSync" step has completed on this job, then:
4. Wait for the result (fail/pass) emails from the remote trybot server.
5. Optionally download the archived artifacts that the trybot uploaded by clicking on the link in the result email.
Attach an optional description to a --remote run to make it easier to identify the results when it finishes.(eg: “testing CL:1234 after fixing NameError”).
The trybot waterfall is organized by bot category. Generally, bot names are <board>-<category>[-group]. E.g., for x86-alex-pre-cq, the category is "pre-cq". For x86-alex-no-vmtest-pre-cq, the category is "no-vmtest-pre-cq". For pineview-release-group, the category is "release".
When you launch your tryjob, cbuildbot will print a link showing where to find your run. For example:
$ cbuildbot -g 288223 --remote rambi-no-vmtest-pre-cq x86-alex-release
Go to https://email@example.com&builder=no-vmtest-pre-cq&builder=release to view the status of your job.
If you want to double check the exact category name of any bot, you can look it up either by launching a tryjob with it (see above), or, for advanced users, by looking in chromite/cbuildbot/config_dump.json (the template is listed as "_template") under the bot name.