| commit | b18d3bf0f8a92b622707f6378d8a7e60eb9078ed | [log] [tgz] |
|---|---|---|
| author | Po-Hsien Wang <pwang@chromium.org> | Wed Mar 13 23:28:33 2019 |
| committer | chrome-bot <chrome-bot@chromium.org> | Fri Mar 15 03:53:36 2019 |
| tree | a677add4c6fd35e07a70ff0fb2e6aed5e6f7a29d | |
| parent | 22eaf3c534a1d88b4a3de8374f82d8703868b2db [diff] |
manifest: add glbench checkout BUG=chromium:941641 TEST=none CQ-DEPEND=CL:*1042649 Change-Id: I2db64b49e7f8d6fa578cf78ebde6cbf7c812baff Signed-off-by: Po-Hsien Wang <pwang@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1522088 Tested-by: Ilja H. Friedel <ihf@chromium.org> Reviewed-by: Ilja H. Friedel <ihf@chromium.org> Reviewed-by: Stéphane Marchesin <marcheu@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.