commit | 1abe71639924afc1adc3a0ff140514efe1669f25 | [log] [tgz] |
---|---|---|
author | chromeos-ci-prod <chromeos-ci-prod@chromeos-bot.iam.gserviceaccount.com> | Sat Apr 16 14:34:33 2022 |
committer | chromeos-ci-prod <chromeos-ci-prod@chromeos-bot.iam.gserviceaccount.com> | Sat Apr 16 14:34:33 2022 |
tree | 7fd95acf33a4e4ce5991b4b6f0a152603e8d50db | |
parent | 2bf4eb6f36c57f3b59571daffdff01569be56275 [diff] |
Syncing with internal manifest Cr-Build-Url: https://cr-buildbucket.appspot.com/build/8816718111230387473 Cr-Automation-Id: cros_source/push_uprevs Change-Id: Ie9e47704c77f13a4258b28c590fb53b2edf7f338
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.