Google Git
Sign in
chromium / chromiumos / manifest / 0c185d3d30e4a174013d29282098c15fbadc5ead
commit0c185d3d30e4a174013d29282098c15fbadc5ead[log] [tgz]
authorNavil Perez <navil@google.com>Tue Jun 02 21:17:11 2020
committerNavil Perez <navil@google.com>Tue Jun 02 21:24:32 2020
tree03645b6021ed359df34e88f1eb853dc00b48d926
parent1237a5a50ec4e719327e8157f383957f3c6350d5 [diff]
full.xml: sync with manifest-internal/full.xml

There is currently an issue with automated syncing between the full.xml
files. Temporarily manually update with crrev.com/i/3067676

BUG=None
TEST=None

Change-Id: Id700143c8813d6e4a80afa67b65fb0330be7dd8d
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/manifest/+/2226999
Tested-by: Navil Perez <navil@google.com>
Auto-Submit: Navil Perez <navil@google.com>
Reviewed-by: Sean Abraham <seanabraham@chromium.org>
Commit-Queue: Sean Abraham <seanabraham@chromium.org>
1 file changed
tree: 03645b6021ed359df34e88f1eb853dc00b48d926
  1. utils/
  2. default.xml ⇨ full.xml
  3. _kernel_upstream.xml
  4. _remotes.xml
  5. full.xml
  6. OWNERS
  7. PRESUBMIT.cfg
  8. README.md
README.md
IMPORTANT: Do not make changes to full.xml in this repo. This repo automatically syncs with the private manifest repo https://chrome-internal.googlesource.com/chromeos/manifest-internal. If you do not have access to the private repo, please ask a Googler to update the manifest on your behalf. The changes must 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.