commit | 59016d643833988b8dbc6e09753e53a7acf5ade5 | [log] [tgz] |
---|---|---|
author | David Riley <davidriley@chromium.org> | Mon Oct 21 20:38:04 2019 |
committer | chrome-bot <chrome-bot@chromium.org> | Tue Oct 22 22:13:44 2019 |
tree | 9917342fd6d618f9c5e3590854dbf6f5e766f990 | |
parent | cbace57857c7785bb61fe2f84d5fb20cf7a4a38f [diff] |
.gitignore: Add some mesa related paths. BUG=None TEST=None Change-Id: I3d3bcee9c2cbf56f14c6e9885cff54325e72a8ea Reviewed-on: https://chromium-review.googlesource.com/1872437 Tested-by: kokoro <noreply+kokoro@google.com> Tested-by: David Riley <davidriley@chromium.org> Commit-Ready: David Riley <davidriley@chromium.org> Legacy-Commit-Queue: Commit Bot <commit-bot@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" --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.