commit | a4728300c0aad2dd89f301752af1e799612f5e38 | [log] [tgz] |
---|---|---|
author | Raju Konduru <rkonduru@google.com> | Wed Mar 06 20:18:46 2019 |
committer | chrome-bot <chrome-bot@chromium.org> | Sat Mar 09 05:20:35 2019 |
tree | fb7eb20365bb395a7a2f49cfcdd0766771163935 | |
parent | b128a19d87d890f0217e69b27e29b96b705adc2c [diff] |
manifest: add kernel 4.14-gw branch checkout BUG=b:127674811 TEST=repo sync CQ-DEPEND=CL:*1010559 Change-Id: Idc613f601cdd63ba93231a5a4070e74263b9e60d Reviewed-on: https://chromium-review.googlesource.com/1506613 Commit-Ready: Raju Konduru <rkonduru@google.com> Tested-by: Raju Konduru <rkonduru@google.com> Reviewed-by: Julan Hsu <julanhsu@google.com> Reviewed-by: Bernie Thompson <bhthompson@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.