.gitignore: Add some mesa related paths.

BUG=None
TEST=None

Change-Id: I3d3bcee9c2cbf56f14c6e9885cff54325e72a8ea
Reviewed-on: https://chromium-review.googlesource.com/1872437
Tested-by: kokoro <noreply+kokoro@google.com>
Tested-by: David Riley <davidriley@chromium.org>
Commit-Ready: David Riley <davidriley@chromium.org>
Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org>
Reviewed-by: Stephen Barber <smbarber@chromium.org>
1 file changed
tree: 9917342fd6d618f9c5e3590854dbf6f5e766f990
  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. scripts/
  22. termina/
  23. .gitignore
  24. COMMIT-QUEUE.ini
  25. LICENSE
  26. OWNERS
  27. README.md
  28. 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" --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.