| commit | a802d184e2e180d117bafca9b2d5d8f7ce987704 | [log] [tgz] |
|---|---|---|
| author | Fergus Dall <sidereal@google.com> | Mon Jul 12 08:53:11 2021 +1000 |
| committer | Commit Bot <commit-bot@chromium.org> | Thu Jul 15 10:31:20 2021 +0000 |
| tree | 0929bacddb996c5ad3b294ba68f9ba817cead14a | |
| parent | a5b805fe5f78d0e384b2c0f342f9031f72a51db9 [diff] |
Re-add component build and upload scripts I've tweaked them from the original form to point at the release builders, which frees us from having to run tryjobs and manually upload debug symbols, and keeps the component as close to the DLC as possible. BUG=chromium:1228109 TEST=Ran scripts Change-Id: I717ca9444acd4daf48912cbc0e219342bf64287d Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/containers/cros-container-guest-tools/+/3020727 Reviewed-by: Nicholas Verne <nverne@chromium.org> Commit-Queue: Fergus Dall <sidereal@google.com> Tested-by: kokoro <noreply+kokoro@google.com>
These are the guest packages for setting up a container to integrate with Chrome OS. This includes build scripts that are run in Google's internal continuous integration service.
The guest packages can be built with Bazel.
bazel build //cros-debs:debs --host_force_python=py2
promote\_apt.sh MILESTONE and promote\_container.sh MILESTONE in scripts are used to promote containers from staging to live. NOTE: Whatever is the latest in staging is what gets promoted to live so make sure it's what was tested.