commit | 0afed92864da73b8927035a1888e0d949a2fed53 | [log] [tgz] |
---|---|---|
author | Stephen Barber <smbarber@chromium.org> | Wed Jul 31 18:23:51 2019 |
committer | chrome-bot <chrome-bot@chromium.org> | Thu Aug 01 01:37:04 2019 |
tree | 1949dc379a0be0f1624e0babf9c9afcc0dee9a1f | |
parent | 85a967eff6ca2da824d4f5b3e3063fff07e62488 [diff] |
container-guest-tools: add nverne to OWNERS BUG=none TEST=none Change-Id: I4038d3957a1aa79bdcfe5398b2d92d546744df73 Reviewed-on: https://chromium-review.googlesource.com/1729090 Tested-by: kokoro <noreply+kokoro@google.com> Tested-by: Stephen Barber <smbarber@chromium.org> Commit-Ready: Stephen Barber <smbarber@chromium.org> Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> Reviewed-by: Nicholas Verne <nverne@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. The CrOS milestone to target and release name (stretch, buster, etc.) are required.
bazel build //... --action_env="MILESTONE=74" --action_env="RELEASE=buster"