README.md 1.28 KB
Newer Older
1
*** note
Kirtika Ruchandani's avatar
Kirtika Ruchandani committed
2
**IMPORTANT**: Changes to this repo must also be made in the private manifest
3 4
repo <https://chrome-internal.googlesource.com/chromeos/manifest-internal>.
Automated sync between manifest-internal and manifest is not yet set up.
5
And, the changes must *also* be synced to the infra/config file
Kirtika Ruchandani's avatar
Kirtika Ruchandani committed
6
chromeos\_repos.star. Without this, the repo will never be picked up by CQ.
7 8 9 10 11
***

# 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
David Jacobo's avatar
David Jacobo committed
12
overridden using `-m`. One could also check out a subset of the manifest using
13 14 15 16 17 18
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
David Jacobo's avatar
David Jacobo committed
19
does include all those needed to create an image.
20 21 22 23 24 25 26 27 28

## 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.