commit | 2271b86cf34d82f19c596c6ae11c7336c8a64896 | [log] [tgz] |
---|---|---|
author | David Riley <davidriley@chromium.org> | Mon Oct 28 16:43:46 2019 |
committer | chrome-bot <chrome-bot@chromium.org> | Tue Oct 29 01:06:25 2019 |
tree | 293ba072164ad57915116e130c88060ca93359ea | |
parent | f45983867d7a421a6c664891841c54d76b4f6b25 [diff] |
mesa/buster: Actually add glbench to list of packages to build. BUG=None TEST=env | grep PACKAGES Change-Id: Ia75d1d22279dc603e1edac0c35698a545c260d7a Reviewed-on: https://chromium-review.googlesource.com/1883997 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.
bazel build //cros-debs:debs --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.