| commit | 0d95a5dad44f0f5e1ff640b1f9dadd8aa1548ac1 | [log] [tgz] |
|---|---|---|
| author | James Ye <jamesye@google.com> | Fri Oct 28 14:24:46 2022 +1100 |
| committer | Chromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Oct 31 00:32:12 2022 +0000 |
| tree | af31f1d8c285891d68748ee2dc9d45dcbdd21218 | |
| parent | b16f9fcbcd6f0b4a33502e38e08712e6c2d70549 [diff] |
kokoro: Reduce number of reprepro calls Pass all debs in each folder to reprepro in one command line, rather than making one execve per deb. BUG=none TEST=kokoro Change-Id: I716f226dd7a30368f487008fcbebd583090f11ff Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/containers/cros-container-guest-tools/+/3989967 Reviewed-by: Fergus Dall <sidereal@google.com> Commit-Queue: James Ye <jamesye@google.com> Tested-by: kokoro <noreply+kokoro@google.com> Reviewed-by: David Munro <davidmunro@google.com> Reviewed-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.