commit | bde3fd492b74225e4d6a934407950caf5db6adce | [log] [tgz] |
---|---|---|
author | chromeos-ci-prod <chromeos-ci-prod@chromeos-bot.iam.gserviceaccount.com> | Tue Jun 07 00:36:27 2022 |
committer | chromeos-ci-prod <chromeos-ci-prod@chromeos-bot.iam.gserviceaccount.com> | Tue Jun 07 00:36:27 2022 |
tree | bfb427385d097612085f34df85b57eecaafcaea9 | |
parent | aa565ab460a365bc3dd9a18a56210868342062e7 [diff] |
Syncing with internal manifest Cr-Build-Url: https://cr-buildbucket.appspot.com/build/8812059916515490769 Cr-Automation-Id: cros_source/push_uprevs Change-Id: I0d1ad0ea61cab7f005adf0d4522f88f3cc50fb4e
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.