| commit | 7a70e29c119544bcae140d700efc357e7d566a93 | [log] [tgz] |
|---|---|---|
| author | James Ye <jamesye@google.com> | Wed Oct 19 18:17:05 2022 +1100 |
| committer | Chromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Oct 24 01:25:02 2022 +0000 |
| tree | 56336c8373e4bfad040fb111dc39d73e25cfcd24 | |
| parent | 93c2855f8bfe1c8726409c9319ee2f6ac5f15b58 [diff] |
kokoro: Use the apt cache bucket for cros_im The cros_im job builds for multiple arches, so it needs to download caches for multiple arches too. BUG=b:254147322 TEST=kokoro Change-Id: Ia765776488d54855013a0a1880212978b2b33cd6 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/containers/cros-container-guest-tools/+/3964139 Commit-Queue: James Ye <jamesye@google.com> Reviewed-by: kokoro <noreply+kokoro@google.com> Reviewed-by: Sophia Lin <sophialin@google.com> Tested-by: kokoro <noreply+kokoro@google.com>
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.