commit | 6662185c2e1ad93554dc226c8e08f9e424798c7e | [log] [tgz] |
---|---|---|
author | Mike Frysinger <vapier@chromium.org> | Wed Aug 16 17:31:53 2017 |
committer | Mike Frysinger <vapier@chromium.org> | Thu Aug 17 03:30:25 2017 |
tree | 431d960dddfc3e0a6d8a7370014d605b4aeb97a3 | |
parent | 35493a92e7141c07cd09ef49be2dc78f9012632a [diff] |
manifest: move libweave to cros remote The libweave branch used by jetstream has been moved to the standard cros remote, and so we can move the project and get rid of the remotes entry for the weave remote. BUG=chromium:649417 TEST=None Change-Id: I28e08d1f65e5f57941ffe3ac3e90d532208fcb3b Reviewed-on: https://chromium-review.googlesource.com/617302 Reviewed-by: Eric Caruso <ejcaruso@chromium.org> Tested-by: Mike Frysinger <vapier@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.