container-guest-tools: Build differentiated stretch and buster packages and containers

* New targets to build just stretch and just buster packages
* Built packages are all placed in a single folder as part of the bazel
build, instead of us needing to copy files around after the build
* Separate output folders for buster/stretch *.deb files
* Kokoro pulls files directly from bazel-bin instead of an intermediate
folder
* Don't build cros-gpu-alpha for Buster
* cros-gpu has different package versions and content for stretch and buster

BUG=chromium:930901
TEST=bazel build per README and compare output files

Change-Id: Ifa90a2793cb5164d70d50db1a8bb54188032d0af
Reviewed-on: https://chromium-review.googlesource.com/1875020
Tested-by: kokoro <noreply+kokoro@google.com>
Tested-by: David Munro <davidmunro@google.com>
Commit-Ready: David Munro <davidmunro@google.com>
Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org>
Reviewed-by: Stephen Barber <smbarber@chromium.org>
30 files changed
tree: 90253a47dd5b9ecc40bb2b5ce897f0bc037e55c1
  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-notificationd/
  10. cros-pulse-config/
  11. cros-sftp/
  12. cros-sommelier/
  13. cros-sommelier-config/
  14. cros-sudo-config/
  15. cros-systemd-overrides/
  16. cros-tast-tests/
  17. cros-ui-config/
  18. cros-wayland/
  19. docs/
  20. kokoro/
  21. lxd/
  22. mesa/
  23. scripts/
  24. termina/
  25. .gitignore
  26. COMMIT-QUEUE.ini
  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.