|author||Mike Frysinger <firstname.lastname@example.org>||Mon Jun 24 18:38:48 2019|
|committer||Commit Bot <email@example.com>||Mon Jun 24 19:21:42 2019|
OWNERS: unify with chromite BUG=None TEST=None Change-Id: Id8d2abaf5ce8cbf1ac5fef3e393e500ca88334f2 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/manifest/+/1672753 Reviewed-by: Ned Nguyen <firstname.lastname@example.org> Reviewed-by: Alex Klein <email@example.com> Commit-Queue: Mike Frysinger <firstname.lastname@example.org> Tested-by: Mike Frysinger <email@example.com>
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.