commit | 5300cb19f4306cdb4a1dbf404cbd3623c88636aa | [log] [tgz] |
---|---|---|
author | Amin Hassani <ahassani@chromium.org> | Tue Feb 25 19:05:28 2020 |
committer | Commit Bot <commit-bot@chromium.org> | Wed Feb 26 21:02:14 2020 |
tree | 3794291f1abbdbbd03c979a7eb8d30d082cace8e | |
parent | fd895181c676fe465288a2586a1b760f2731e96e [diff] |
manifest: Uprev puffin to the latest commit. We need to get aosp/1240207 into Chrome OS but since dev-util/puffin does not have a Chrome OS branch, the only way to do this cherrypick is upreving the revision in the manifest itself and then upreving the ebuild. This CL uprevs the public manifest. BUG=chromium:1050869 TEST=sudo FEATURES=test emerge puffin Cq-Depend: chrome-internal:2632641 Change-Id: If8978e64e6140567318e160a2c6a93083349e419 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/manifest/+/2072700 Tested-by: Amin Hassani <ahassani@chromium.org> Reviewed-by: Jae Hoon Kim <kimjae@chromium.org> Commit-Queue: Amin Hassani <ahassani@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 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.