| commit | 6590dcea9683c7c52f61a63b570f2232262d79f9 | [log] [tgz] |
|---|---|---|
| author | Don Garrett <dgarrett@google.com> | Fri Oct 19 17:18:42 2018 |
| committer | chrome-bot <chrome-bot@chromium.org> | Mon Oct 22 20:40:08 2018 |
| tree | 48b48aed85e77d62df6e377e48255bd73182f84b | |
| parent | 9becc45b23397015c3777e7556de4ea029fb1db4 [diff] |
full: Update depot_tools pin. Update depot_tools pin to the most current version. BUG=None TEST=None Change-Id: I919a1670a421629ddc3b8991ffd71ff6d5bab9f6 Reviewed-on: https://chromium-review.googlesource.com/1291870 Commit-Ready: Don Garrett <dgarrett@chromium.org> Tested-by: Don Garrett <dgarrett@chromium.org> Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Reviewed-by: Mike Nichols <mikenichols@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.