commit | cd1012fb2516a7b05cfe386ea99e5f2541799584 | [log] [tgz] |
---|---|---|
author | Fergus Dall <sidereal@google.com> | Fri May 15 03:26:01 2020 |
committer | Commit Bot <commit-bot@chromium.org> | Tue May 19 01:17:49 2020 |
tree | 649f4937946ce225b31bcea42116fa38193c97c6 | |
parent | eca7abe06c717c4281b2655eccbb867cd1c452f9 [diff] |
kokoro: Remove code for tracking if we're in presubmit Kokoro won't let us run apt_signer in presubmit even as a no-op, so we have to skip it by duplicating the entire config chain in google3. This means we no longer need any special handling of the difference here because apt_signer, publish_apt_staging, and publish_lxd_staging just won't run at all. BUG=none TEST=kokoro Change-Id: I3d037e77f8f76762e2be78e5a23739c0cc35b0aa Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/containers/cros-container-guest-tools/+/2203503 Reviewed-by: Nicholas Verne <nverne@chromium.org> Commit-Queue: Fergus Dall <sidereal@google.com> Tested-by: kokoro <noreply+kokoro@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.