commit | 08b331d654e418933aa508449279df1622fc4422 | [log] [tgz] |
---|---|---|
author | Nicholas Hollingum <hollingum@google.com> | Wed Dec 09 01:38:27 2020 |
committer | Commit Bot <commit-bot@chromium.org> | Fri Jan 22 07:46:17 2021 |
tree | ed975f23d917206f55bfc62ce347802c902e1ce6 | |
parent | 5f932aa065a2990756898e871551ff173acc72be [diff] |
cros-sommelier: Rename --master to --parent In line with go/coil. This depends on the sommelier change in crrev.com/c/2580959 and as such should only be submitted once we pass a milestone where that change is present. BUG=b:172846445 TEST=tbd Change-Id: I32951d29c89bd1bc9c0908edb0c096ea16b55aef Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/containers/cros-container-guest-tools/+/2581098 Tested-by: Nic Hollingum <hollingum@google.com> Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: Fergus Dall <sidereal@google.com> Reviewed-by: David Munro <davidmunro@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.
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.