| commit | a93ea0425059ffc9efad88bf99aab3c1207b7b68 | [log] [tgz] |
|---|---|---|
| author | David Riley <davidriley@chromium.org> | Fri Sep 27 03:32:13 2019 |
| committer | chrome-bot <chrome-bot@chromium.org> | Fri Oct 11 20:18:28 2019 |
| tree | 2f45ac9724ac922f2b9896dd6dee9415aa2be441 | |
| parent | 2c07dfa6d0f2a21abb8fb221ff0d21be8ebd3d3f [diff] |
kokoro: Build buster mesa using kokoro checkout. BUG=chromium:979461 TEST=None Change-Id: Iaef96b8bade56363fbf4d368e285197b0696629b Reviewed-on: https://chromium-review.googlesource.com/1828353 Tested-by: kokoro <noreply+kokoro@google.com> Commit-Ready: Stephen Barber <smbarber@chromium.org> Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> Reviewed-by: 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. 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
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.