| commit | 73823c301f36dcecc78000b0eaad94e4c6860d1a | [log] [tgz] |
|---|---|---|
| author | David Munro <davidmunro@google.com> | Tue Oct 29 16:30:53 2019 +1100 |
| committer | chrome-bot <chrome-bot@chromium.org> | Tue Oct 29 03:20:42 2019 -0700 |
| tree | 161ab8e33a85b92cb6f2fa126dd5836e8a125895 | |
| parent | 2271b86cf34d82f19c596c6ae11c7336c8a64896 [diff] |
container-guest-tools: Fix cros-gpu-stretch BUG=None TEST=Verify output paths in build .deb, verify an lxd image with corrected paths builds. Change-Id: I43aacecb51d23ee46a7598f1f566e533148263c0 Reviewed-on: https://chromium-review.googlesource.com/1886132 Tested-by: kokoro <noreply+kokoro@google.com> Tested-by: David Munro <davidmunro@google.com> Commit-Ready: David Munro <davidmunro@google.com> Commit-Ready: Stephen Barber <smbarber@chromium.org> Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> Reviewed-by: Stephen Barber <smbarber@chromium.org> Reviewed-by: David Riley <davidriley@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.