container-guest-tools: add nverne to OWNERS

BUG=none
TEST=none

Change-Id: I4038d3957a1aa79bdcfe5398b2d92d546744df73
Reviewed-on: https://chromium-review.googlesource.com/1729090
Tested-by: kokoro <noreply+kokoro@google.com>
Tested-by: Stephen Barber <smbarber@chromium.org>
Commit-Ready: Stephen Barber <smbarber@chromium.org>
Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org>
Reviewed-by: Nicholas Verne <nverne@chromium.org>
Reviewed-by: Stephen Barber <smbarber@chromium.org>
1 file changed
tree: 1949dc379a0be0f1624e0babf9c9afcc0dee9a1f
  1. cros-adapta/
  2. cros-apt-config/
  3. cros-garcon/
  4. cros-gpu/
  5. cros-gpu-alpha/
  6. cros-guest-tools/
  7. cros-notificationd/
  8. cros-pulse-config/
  9. cros-sftp/
  10. cros-sommelier/
  11. cros-sommelier-config/
  12. cros-sudo-config/
  13. cros-systemd-overrides/
  14. cros-tast-tests/
  15. cros-ui-config/
  16. cros-wayland/
  17. docs/
  18. kokoro/
  19. lxd/
  20. mesa/
  21. termina/
  22. .gitignore
  23. COMMIT-QUEUE.ini
  24. LICENSE
  25. OWNERS
  26. README.md
  27. 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. The CrOS milestone to target and release name (stretch, buster, etc.) are required.

bazel build //... --action_env="MILESTONE=74" --action_env="RELEASE=buster"