commit | ec3695e6cc024a5daee36343aec87cbc74f9ec54 | [log] [tgz] |
---|---|---|
author | David Valleau <valleau@chromium.org> | Thu Jul 19 21:45:51 2018 |
committer | chrome-bot <chrome-bot@chromium.org> | Tue Jul 24 23:19:51 2018 |
tree | 117d98a33af733600282444099a3a7ed611df1db | |
parent | 89a3313db35391ce8bf2935336692d830d09f2a3 [diff] |
Adding cups to the public manifest BUG=chromium:865217 TEST=None Change-Id: Ib5fe38a88713b471ea8af2ccd84c2c600a156293 Reviewed-on: https://chromium-review.googlesource.com/1144320 Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com> Tested-by: David Valleau <valleau@chromium.org> Reviewed-by: Sean Kau <skau@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.