commit | 83311f98f1b6c5a62e0f5a5c9f1d03e44f4327c1 | [log] [tgz] |
---|---|---|
author | Fergus Dall <sidereal@google.com> | Tue Jun 30 02:10:03 2020 +1000 |
committer | Commit Bot <commit-bot@chromium.org> | Tue Jun 30 11:41:37 2020 +0000 |
tree | 41b3ced558b201024156f3aea9cd72bfdd21ce24 | |
parent | f1345e683176df85615e261777686eebac613abe [diff] |
Apply linter to all bazel files This appears to now be a presubmit check BUG=none TEST=CQ Change-Id: Idfc3a5be03a21af0806a7f7df745a8745e728475 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/containers/cros-container-guest-tools/+/2272641 Reviewed-by: David Munro <davidmunro@google.com> Reviewed-by: Nicholas Verne <nverne@chromium.org> Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: Nicholas Verne <nverne@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.