commit | aa2a5e3fba2e0458432b11472735050c5b0f6310 | [log] [tgz] |
---|---|---|
author | Bernie Thompson <bhthompson@google.com> | Wed Apr 12 17:53:39 2017 |
committer | chrome-bot <chrome-bot@chromium.org> | Wed Apr 12 23:07:52 2017 |
tree | 8e0d1ad77ce86f5aeabb4c7b440f62c8c056caa1 | |
parent | 345da0422134d398765a52716c42f946cb7d3904 [diff] |
Add new updater repos to the manifest This adds in: displaylink-updater realtek-updater sis-updater BUG=chromium:709816 TEST=None Change-Id: I549342e6283460a79cfd6d5275fffbb4ef6bef02 Reviewed-on: https://chromium-review.googlesource.com/475754 Commit-Ready: Bernie Thompson <bhthompson@chromium.org> Tested-by: Bernie Thompson <bhthompson@chromium.org> Reviewed-by: Katie Roberts-Hoffman <katierh@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.