| commit | e2f4f7a1794fa9f150a4566285e9df139fe83280 | [log] [tgz] |
|---|---|---|
| author | Fergus Dall <sidereal@google.com> | Tue Jun 01 13:46:46 2021 +1000 |
| committer | Commit Bot <commit-bot@chromium.org> | Tue Jul 20 07:11:00 2021 +0000 |
| tree | 83a4658564436bc5c9b598b4a980ddc75f66a70a | |
| parent | 6d56ad82309f769c443c4923e8ef64409ab3c3fe [diff] |
Start building bullseye containers This is somewhat experimental, but since bullseye is getting close to release it shouldn't change out from under us much. BUG=chromium:1217902 TEST=kokoro Change-Id: I6d43907ee5321e7b9ce88b0301ce6c7f2f5a41fd Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/containers/cros-container-guest-tools/+/2929060 Reviewed-by: Nicholas Verne <nverne@chromium.org> Reviewed-by: David Munro <davidmunro@google.com> Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: Fergus Dall <sidereal@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.