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>
6 files changed
tree: 649f4937946ce225b31bcea42116fa38193c97c6
  1. cros-adapta/
  2. cros-apt-config/
  3. cros-debs/
  4. cros-garcon/
  5. cros-gpu-alpha/
  6. cros-gpu-buster/
  7. cros-gpu-stretch/
  8. cros-guest-tools/
  9. cros-host-fonts/
  10. cros-notificationd/
  11. cros-pulse-config/
  12. cros-sftp/
  13. cros-sommelier/
  14. cros-sommelier-config/
  15. cros-sudo-config/
  16. cros-systemd-overrides/
  17. cros-tast-tests/
  18. cros-ui-config/
  19. cros-wayland/
  20. docs/
  21. kokoro/
  22. lxd/
  23. mesa/
  24. scripts/
  25. termina/
  26. .gitignore
  27. LICENSE
  28. OWNERS
  29. PRESUBMIT.cfg
  30. README.md
  31. WORKSPACE
README.md

cros-container-guest-tools

Overview

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.

Building

The guest packages can be built with Bazel.

bazel build //cros-debs:debs --host_force_python=py2

Releasing

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.