| commit | 2c07dfa6d0f2a21abb8fb221ff0d21be8ebd3d3f | [log] [tgz] |
|---|---|---|
| author | David Munro <davidmunro@google.com> | Fri Sep 27 14:31:25 2019 +1000 |
| committer | chrome-bot <chrome-bot@chromium.org> | Mon Sep 30 22:38:49 2019 -0700 |
| tree | 415a3e141acbc1f4f3a7a871b966f9eddce4314d | |
| parent | 41a43eaae4e8560ad4d3c8eb3f7f3e1fcb3c0a74 [diff] |
container-guest-tools: Import release scripts from old infra repo TEST=none BUG=none Change-Id: Ia4b2c55e581d229f67031181dad8739400fa119b Reviewed-on: https://chromium-review.googlesource.com/1826699 Tested-by: kokoro <noreply+kokoro@google.com> Tested-by: David Munro <davidmunro@google.com> Commit-Ready: David Munro <davidmunro@google.com> Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> Reviewed-by: Fergus Dall <sidereal@google.com> 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.