cros-sommelier: Rename --master to --parent

In line with go/coil.

This depends on the sommelier change in crrev.com/c/2580959 and as such
should only be submitted once we pass a milestone where that change is
present.

BUG=b:172846445
TEST=tbd

Change-Id: I32951d29c89bd1bc9c0908edb0c096ea16b55aef
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/containers/cros-container-guest-tools/+/2581098
Tested-by: Nic Hollingum <hollingum@google.com>
Tested-by: kokoro <noreply+kokoro@google.com>
Commit-Queue: Fergus Dall <sidereal@google.com>
Reviewed-by: David Munro <davidmunro@google.com>
2 files changed
tree: ed975f23d917206f55bfc62ce347802c902e1ce6
  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-logging/
  11. cros-notificationd/
  12. cros-pulse-config/
  13. cros-sftp/
  14. cros-sommelier/
  15. cros-sommelier-config/
  16. cros-sudo-config/
  17. cros-systemd-overrides/
  18. cros-tast-tests/
  19. cros-ui-config/
  20. cros-wayland/
  21. docs/
  22. kokoro/
  23. lxd/
  24. mesa/
  25. scripts/
  26. termina/
  27. .gitignore
  28. LICENSE
  29. OWNERS
  30. PRESUBMIT.cfg
  31. README.md
  32. 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.