commit | 3842a7d95fddc933d7665c6fdb485e4941828adf | [log] [tgz] |
---|---|---|
author | Stephen Barber <smbarber@chromium.org> | Fri Apr 12 11:14:12 2019 -0700 |
committer | Stephen Barber <smbarber@chromium.org> | Fri Apr 12 19:30:41 2019 +0000 |
tree | 1529476c58992e86570242e7357c54c1fb789736 | |
parent | 55741734edd5fb06ecbb64266e458bde93097726 [diff] |
kokoro: update apt_signer to force using subkey BUG=chromium:952214 TEST=apt update succeeds Change-Id: I90eebf04a8d8ec1034c78c920c715ea65a448677 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/containers/cros-container-guest-tools/+/1565092 Reviewed-by: Dylan Reid <dgreid@chromium.org> Reviewed-by: David Riley <davidriley@chromium.org> Commit-Queue: Stephen Barber <smbarber@chromium.org> Tested-by: Stephen Barber <smbarber@chromium.org> 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. The CrOS milestone to target and release name (stretch, buster, etc.) are required.
bazel build //... --action_env="MILESTONE=74" --action_env="RELEASE=buster"