commit | 698a0d6e667fd290582032b67ac3171b680d0718 | [log] [tgz] |
---|---|---|
author | chromeos-ci-prod <chromeos-ci-prod@chromeos-bot.iam.gserviceaccount.com> | Fri Feb 04 21:09:16 2022 |
committer | chromeos-ci-prod <chromeos-ci-prod@chromeos-bot.iam.gserviceaccount.com> | Fri Feb 04 21:09:16 2022 |
tree | 49bdd0e54d8630a847be04789987b882c600bbd5 | |
parent | 6b1817ad324b3527ef914bf383a4bc179ad1ed0b [diff] |
Syncing with internal manifest Cr-Build-Url: https://cr-buildbucket.appspot.com/build/8823125957477874481 Cr-Automation-Id: cros_source/push_uprevs Change-Id: I486ae20973cb419eb3534ea4844a1c642a19e1e7
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.