commit | 7563ab539b5754df47cb3ec9c14f42836e0eb726 | [log] [tgz] |
---|---|---|
author | Judy Wu <jinrongwu@google.com> | Thu Oct 15 02:03:00 2020 |
committer | Commit Bot <commit-bot@chromium.org> | Wed Oct 28 22:10:18 2020 |
tree | b8002fc10a1c8e2a1bd692d54355570506c666c7 | |
parent | 19eab9efa1317f4086d95adaa94d57378dc82075 [diff] |
Create a large container to test apps Create a large container and pre-install all the apps in it BUG=chromium:1101583 TEST=None Change-Id: Ife466f5aa6bd2308272efefec3689eced89ce397 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/containers/cros-container-guest-tools/+/2473973 Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: Judy Wu <jinrongwu@google.com> Reviewed-by: David Munro <davidmunro@google.com> Reviewed-by: Fergus Dall <sidereal@google.com> Reviewed-by: Matthew Warton <mwarton@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.