kokoro: Set a long timeout on mesa builds.

The default 180 timeout isn't enough for our heavyweight qemu
builds.

BUG=chromium:979461
TEST=Hope is the strategy

Change-Id: I2700c6568882c2886379b54ae045bee757c5894e
Reviewed-on: https://chromium-review.googlesource.com/1788418
Tested-by: kokoro <noreply+kokoro@google.com>
Tested-by: Nicholas Verne <nverne@chromium.org>
Commit-Ready: Nicholas Verne <nverne@chromium.org>
Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org>
Reviewed-by: Stephen Barber <smbarber@chromium.org>
2 files changed
tree: 9b99528129b8ae1de4b7cc30e28d284b1af5b779
  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"