commit | ca75f7522b47f4d5fbd25d569082ad1c50187e35 | [log] [tgz] |
---|---|---|
author | Stephen Barber <smbarber@chromium.org> | Tue May 28 18:56:00 2019 -0700 |
committer | chrome-bot <chrome-bot@chromium.org> | Thu May 30 14:13:36 2019 -0700 |
tree | 8fb49bf4a280024cc022ff3332c251e6cd77370d | |
parent | 1688ac5bd43a4f5f04e31b6e381bcb67f98f44f2 [diff] |
container-guest-tools: add OWNERS file BUG=none TEST=none Change-Id: I543a421cbab5b6b6322ff3cf651cc11adf32abc2 Reviewed-on: https://chromium-review.googlesource.com/1633493 Commit-Ready: Stephen Barber <smbarber@chromium.org> Tested-by: kokoro <noreply+kokoro@google.com> Tested-by: Stephen Barber <smbarber@chromium.org> Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> Reviewed-by: Chris McDonald <cjmcdonald@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"