commit | 3d3ab7dad64091a64fcd50d4b75a2573c4ecf5cc | [log] [tgz] |
---|---|---|
author | Stephen Barber <smbarber@chromium.org> | Tue Sep 24 11:09:01 2019 -0700 |
committer | Stephen Barber <smbarber@chromium.org> | Tue Sep 24 18:11:51 2019 +0000 |
tree | ea1131da69fa5242b7e6110ccbc8825edc05a47b | |
parent | 43213c8a647910c460a032155cf5b3a994974700 [diff] |
kokoro: use per-release artifact paths for mesa debs BUG=chromium:979461 TEST=kokoro Change-Id: I35507095613b66c925c11d9df27630d44182abf8 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/containers/cros-container-guest-tools/+/1822578 Reviewed-by: Stephen Barber <smbarber@chromium.org> Commit-Queue: Stephen Barber <smbarber@chromium.org> Tested-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" --host_force_python=py2