commit | f45983867d7a421a6c664891841c54d76b4f6b25 | [log] [tgz] |
---|---|---|
author | David Munro <davidmunro@google.com> | Thu Oct 17 18:56:42 2019 +1100 |
committer | chrome-bot <chrome-bot@chromium.org> | Sun Oct 27 20:55:37 2019 -0700 |
tree | 90253a47dd5b9ecc40bb2b5ce897f0bc037e55c1 | |
parent | 9a017c4a428b9d88ed914d9b6fc382fa0d3a3f2f [diff] |
container-guest-tools: Build differentiated stretch and buster packages and containers * New targets to build just stretch and just buster packages * Built packages are all placed in a single folder as part of the bazel build, instead of us needing to copy files around after the build * Separate output folders for buster/stretch *.deb files * Kokoro pulls files directly from bazel-bin instead of an intermediate folder * Don't build cros-gpu-alpha for Buster * cros-gpu has different package versions and content for stretch and buster BUG=chromium:930901 TEST=bazel build per README and compare output files Change-Id: Ifa90a2793cb5164d70d50db1a8bb54188032d0af Reviewed-on: https://chromium-review.googlesource.com/1875020 Tested-by: kokoro <noreply+kokoro@google.com> Tested-by: David Munro <davidmunro@google.com> Commit-Ready: David Munro <davidmunro@google.com> Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> Reviewed-by: Stephen Barber <smbarber@chromium.org>
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.