Google Git
Sign in
chromium / chromiumos / manifest / ca51f35803b67a755b34bbb47727e141b364ab74
commitca51f35803b67a755b34bbb47727e141b364ab74[log] [tgz]
authorMike Frysinger <vapier@chromium.org>Thu Jan 10 19:48:57 2019
committerchrome-bot <chrome-bot@chromium.org>Mon Jan 14 00:30:32 2019
tree4152a1cb0999945c6c0e81501130f4bec9fa61c1
parent1f76f71df1e111dba793365d7dd4a4ab467954f9 [diff]
roll depot_tools for newer repo

BUG=chromium:900461
TEST=precq passes

Change-Id: I08b707f50f3a015a092e68ed1e566bae287ca65e
Reviewed-on: https://chromium-review.googlesource.com/1405550
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
Reviewed-by: Don Garrett <dgarrett@chromium.org>
1 file changed
tree: 4152a1cb0999945c6c0e81501130f4bec9fa61c1
  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.