commit | 1cd40747ebb3d003b9603bd6a53719850108cc0e | [log] [tgz] |
---|---|---|
author | James Ye <jamesye@google.com> | Fri Oct 28 18:22:51 2022 +1100 |
committer | Chromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Oct 31 23:12:22 2022 +0000 |
tree | be06f1ce3e70f32e274e1e68fd2eea2af67f1a90 | |
parent | 0d95a5dad44f0f5e1ff640b1f9dadd8aa1548ac1 [diff] |
lxd: Reduce number of apt-get calls Batch package installs into one apt-get call per container setup. Also: * Remove the debian testing repo/pins which were unused. * Add xterm to the test image for crostini.InputLatency. * Remove the hold on vscode - we should never be installing updates during a test so this doesn't do anything. BUG=none TEST=kokoro Change-Id: Ib1bf14e213a872f42e58019d283f5d761ee0b272 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/containers/cros-container-guest-tools/+/3989968 Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: James Ye <jamesye@google.com> Reviewed-by: David Munro <davidmunro@google.com> Reviewed-by: kokoro <noreply+kokoro@google.com> Reviewed-by: Fergus Dall <sidereal@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.