| commit | 1d204a49bcd2e3bcf836c34f72a779d4ab89472a | [log] [tgz] |
|---|---|---|
| author | Nicholas Hollingum <hollingum@google.com> | Thu Mar 12 11:34:56 2020 +1100 |
| committer | Commit Bot <commit-bot@chromium.org> | Thu Mar 12 03:13:57 2020 +0000 |
| tree | d89c387505c98c3af2d12e5688d3e76d6d116f52 | |
| parent | d2e19d887deee1f748b1b06918903e9f3a306818 [diff] |
container-guest-tools: Fix the kokoro build. The kokoro build is broken as of 28th Feb, due to two things: - the docker images can not apt-get from a https repo - guest_tools build machine has a corrupted bazel config This cl fixes both issues, also i have uploaded new stretch/buster docker images to /google/data/rw/teams/chromeos-vm/docker. BUG=chromium:1060811 TEST=presubmit Change-Id: I02270706ec0f7692461515c70a780dc469a7d561 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/containers/cros-container-guest-tools/+/2099682 Reviewed-by: David Munro <davidmunro@google.com> Commit-Queue: Nic Hollingum <hollingum@google.com> Tested-by: Nic Hollingum <hollingum@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.