|author||chromeos-ci-prod <email@example.com>||Wed May 04 12:35:09 2022|
|committer||chromeos-ci-prod <firstname.lastname@example.org>||Wed May 04 12:35:09 2022|
Syncing with internal manifest Cr-Build-Url: https://cr-buildbucket.appspot.com/build/8815094915524437425 Cr-Automation-Id: cros_source/push_uprevs Change-Id: Iee3329986b18495d94c4070f648e214a8c963bf7
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 overridden 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 image.
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.