commit | 8c4e9fd2ec10efb2528de180b5813a309eb43026 | [log] [tgz] |
---|---|---|
author | Prathmesh Prabhu <pprabhu@chromium.org> | Tue Oct 30 16:47:01 2018 |
committer | Prathmesh Prabhu <pprabhu@chromium.org> | Wed Oct 31 16:25:18 2018 |
tree | 39387eb3c8f97bd5606d78ee8ad88dba7018bbce | |
parent | 3977b84ed8f4686c0d487d99c14a60ad2971f012 [diff] |
Add swarming client library to labtools group BUG=chromium:900005 TEST=None Change-Id: I216edebb91f48b62dc66c92f5950d452d9ec5e60 Reviewed-on: https://chromium-review.googlesource.com/c/1307776 Tested-by: Prathmesh Prabhu <pprabhu@chromium.org> Trybot-Ready: Prathmesh Prabhu <pprabhu@chromium.org> Reviewed-by: Aviv Keshet <akeshet@chromium.org>
Repo is the tool that we use to manage our local checkouts. It parses the manifest specified by the default.xml
file. The name of the manifest can be ovverriden using -m
. One could also check out a subset of the manifest using the repo groups
feature. This section documents the important groups that are part of the default chromiumos manifest.
This group is the minimum subset of repos needed to do a full build of Chrome OS. It doesn't include all of the repos to necessarily test the OS image but does include all those needed to create an iamge.
The subset of repos needed to perform release actions i.e. payload generation, etc. Used by release engineers, TPMs, and Infra team members. Note this group isn't useful without a checkout of manifest-internal.
Tools needed to perform routine lab administrative actions like DUT re-allocation or lab server management.