| commit | 589dced034f6321beec7027a778985a6458429b6 | [log] [tgz] |
|---|---|---|
| author | Mike Frysinger <vapier@chromium.org> | Mon Oct 17 22:10:01 2016 |
| committer | chrome-bot <chrome-bot@chromium.org> | Sat Oct 29 17:41:44 2016 |
| tree | 29b1dbd77ce3e7b4768eb9dfb1f9fdd20f9a62ff | |
| parent | 3f00c45ad8358af82ceef95dfe4b3001264c4b96 [diff] |
depot_tools: update for newer repo BUG=chromium:632203 TEST=precq still passes Change-Id: If69f0ce172f73c0f76ed3896c8cca875bf9a735e Reviewed-on: https://chromium-review.googlesource.com/400058 Commit-Ready: Mike Frysinger <vapier@chromium.org> Tested-by: Mike Frysinger <vapier@chromium.org> Reviewed-by: Don Garrett <dgarrett@chromium.org>
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.
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.
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.
Tools needed to perform routine lab administrative actions like DUT re-allocation or lab server management.