| commit | 3177b41cb7647074f77999764958ff20883d724d | [log] [tgz] |
|---|---|---|
| author | Stephen Barber <smbarber@chromium.org> | Fri Oct 25 12:26:45 2019 |
| committer | chrome-bot <chrome-bot@chromium.org> | Fri Oct 25 19:59:50 2019 |
| tree | b9521c66dacd360fa0134aa569cf2d7bc3ad2d7f | |
| parent | 622a9edd64fe4f31c46064b5e59c78dc5d9ac629 [diff] |
termina: only create vm_tools.img if cros-containers dir exists BUG=chromium:1018185 TEST=termina_build_image on sludge Change-Id: Ied2a68aebd59c84cda3094df80ee0603e952e038 Reviewed-on: https://chromium-review.googlesource.com/1880984 Tested-by: kokoro <noreply+kokoro@google.com> Tested-by: Victor-Gabriel Savu <vsavu@google.com> Tested-by: Stephen Barber <smbarber@chromium.org> Commit-Ready: Stephen Barber <smbarber@chromium.org> Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Victor-Gabriel Savu <vsavu@google.com>
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.