commit	053cf6a2ec4315b52cc3992d977d0ca02bf6c0f3	[log] [tgz]
author	YH Lin <yueherngl@google.com>	Wed Feb 26 17:16:01 2020
committer	YH Lin <yueherngl@google.com>	Wed Feb 26 17:16:01 2020
tree	54a045daef0b83893e0263f5e98f51bd43fcfc5d
parent	39bcf72c9f96ebd540551691bfca19afb9785890 [diff]

tree: 54a045daef0b83893e0263f5e98f51bd43fcfc5d

README.md

IMPORTANT: Changes to this repo must also be made in the private manifest repo https://chrome-internal.googlesource.com/chromeos/manifest-internal. Automated sync between manifest-internal and manifest is not yet set up. And, the changes must also be synced to the infra/config file chromeos_repos.star. Without this, the repo will never be picked up by CQ.

Repo Groups

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.

minilayout

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.

buildtools

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.

labtools

Tools needed to perform routine lab administrative actions like DUT re-allocation or lab server management.