commit | 9aeae22b4b80a675f141070ba97f6a1521e63a15 | [log] [tgz] |
---|---|---|
author | Sophia Lin <sophialin@google.com> | Wed Aug 24 01:37:51 2022 +0000 |
committer | Chromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Aug 29 02:07:23 2022 +0000 |
tree | 83b2614f4e1f39fc45a029eea66e5b40193d7fe7 | |
parent | a48a7c1f104b040e8bdd5907a55f4ff409959159 [diff] |
kokoro: Add vm_tools/ to IME job paths Since IME requires files from the parent dir files for sommelier, kokoro will need to checkout vm_tools/ instead of only cros_im/. The build script will be run from git/vm_tools/cros_im/. The resultant artifacts will be in git/vm_tools/cros_im/cros_im_debs/*_cros_im_debs, which are copied into the kokoro artifacts directory. BUG=b:232047698,chromium:1312296 TEST=To be tested when google3 kokoro jobs run Change-Id: I668679e924bc07351f6a0d72b5aa264601b0bb4b Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/containers/cros-container-guest-tools/+/3852339 Reviewed-by: Fergus Dall <sidereal@google.com> Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: Sophia Lin <sophialin@google.com> Reviewed-by: Timothy Loh <timloh@chromium.org>
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.
The guest packages can be built with Bazel.
bazel build //cros-debs:debs
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.