commit | 5e50bca350e730b73b81d5707bf332c12efd5c82 | [log] [tgz] |
---|---|---|
author | Drew Davenport <ddavenport@chromium.org> | Wed May 24 15:06:29 2017 |
committer | chrome-bot <chrome-bot@chromium.org> | Fri May 26 00:16:02 2017 |
tree | 0654edaf0f8a33d3439e6e1ba0060aaa1a603ef6 | |
parent | c546289bc49733bffbe8deeeec53728759787b2d [diff] |
Remove ply-image from manifest It's usage has been replaced by frecon and is no longer used. BUG=chromium:691762 TEST=remote trybot passes Change-Id: If4b79e4babb5b4761eaeabe93e272a2b0b4cb16c Reviewed-on: https://chromium-review.googlesource.com/513481 Commit-Ready: Drew Davenport <ddavenport@chromium.org> Tested-by: Drew Davenport <ddavenport@chromium.org> Reviewed-by: Dan Erat <derat@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.