commit | ec9b237418eafb6bcdc250cfdc1d2b4a6fc98455 | [log] [tgz] |
---|---|---|
author | Jack Neus <jackneus@google.com> | Mon Apr 12 20:28:25 2021 |
committer | Commit Bot <commit-bot@chromium.org> | Mon Apr 12 22:42:57 2021 |
tree | 437133c0a1da0d7c391dd4f1d17e055805ff2f13 | |
parent | 87c05486e6e5426d6a0add82d9b700e759217fc8 [diff] |
Manually repair R91 external manifest BUG=b:184966242 TEST=none Change-Id: Iee167a938a66d0c3a891871421c046579db08685 Cq-Depends: chrome-internal:3755402 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/manifest/+/2822679 Commit-Queue: Jack Neus <jackneus@google.com> Tested-by: Jack Neus <jackneus@google.com> Reviewed-by: LaMont Jones <lamontjones@chromium.org> Reviewed-by: George Engelbrecht <engeg@google.com>
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 overridden 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 image.
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.