Google Git
Sign in
chromium / chromiumos / manifest / e787a2fa32bf4166805b153513b5caf44ddfc0fe
commite787a2fa32bf4166805b153513b5caf44ddfc0fe[log] [tgz]
authorDavid Valleau <valleau@chromium.org>Mon Aug 27 21:50:46 2018
committerchrome-bot <chrome-bot@chromium.org>Wed Sep 19 00:54:57 2018
tree218a6d0d467039c34a289d405d592b884fe9c261
parent3985c04147ea7c9257f297b21223380f8a7ea0b4 [diff]
Changing manifest to point to the cups-2-2-8 branch

BUG=chromium:865219
TEST=None
CQ-DEPEND=CL:1191985

Change-Id: I4966183f659c0bfab8f34c97c04d46a54b34a489
Reviewed-on: https://chromium-review.googlesource.com/1192229
Commit-Ready: David Valleau <valleau@chromium.org>
Tested-by: David Valleau <valleau@chromium.org>
Reviewed-by: Sean Kau <skau@chromium.org>
1 file changed
tree: 218a6d0d467039c34a289d405d592b884fe9c261
  1. default.xml ⇨ full.xml
  2. _remotes.xml
  3. full.xml
  4. README.md
README.md
IMPORTANT: Changes to this repo must also be made in the private manfest repo https://chrome-internal.googlesource.com/chromeos/manifest-internal. Automated sync between manifest-internal and manifest is not yet set up.

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 ovverriden 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 iamge.

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.