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 normal build run with a set of your changes. The changes are applied to tip of tree (ToT).
It supports building both Gerrit CLs as well as changes you‘ve committed locally but haven’t yet uploaded.
See the remote tryjobs list for a list of running jobs.
Run the following to see a list of common configs:
$ cros tryjob --list
See the full set of options:
$ cros tryjob --help
@chromium.org
account, you can run cipd auth-logout && cipd auth-login
to switch to your @google.com
account.$ cros tryjob -g [*]<cl_1> [-g ...] config [config...]
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.
$ cros tryjob -g 4168 -g *1234 caroline-llvm-toolchain-tryjob caroline-release-tryjob
This runs a tryjob for the caroline-llvm-toolchain
and caroline-release
configs in parallel. It applies two CL's:
In the case where a CL has several patches associated with it, the latest patch is used.
$ cros tryjob -p <project1>[:<branch1>] [-p ...] config [config..]
Specify the name of the project (not the path, look for Project:
in repo info
) and optionally the project branch. If no branch is specified the current branch of the project will be used.
$ cros tryjob -p chromiumos/chromite -p chromiumos/overlays/chromiumos-overlay:my_branch amd64-generic-unittest-stress
This patches in any commits in project chromiumos/chromite's current branch and on branch my_branch
in project chromiumos/overlays/chromiumos-overlay
.
To test patches for a release branch (i.e., R79, R80) use the --branch
(-b
) option with -g
:
(outside) $ ~/chromiumos/chromite/bin/cros tryjob -b release-R79-12607.B -g 1906723 nocturne-release-tryjob
cros
from a ToT checkout and not just the local checkout, which is why the above command shows the full path.The --production
flag allows triggering an official release build. You should consult with the Chrome OS CI Bobby before using.
Trigger a release build using ToT for the hatch
board:
$ cros tryjob --production hatch-release
Trigger a release build using the R79 branch (release-R79-12607.B
) for the hatch
board:
$ cros tryjob --production --branch release-R79-12607.B hatch-release
When you launch your tryjob, it will print a link showing where to find your run.
For example:
$ cros tryjob -g 288223 caroline-release-tryjob Verifying patches... Submitting tryjob... Tryjob submitted! To view your tryjobs, visit: https://ci.chromium.org/b/12345678
You can also search for jobs created by a specific user (email address).