commit | 28f04a1d275460a1a91d979aecefd53c33b1b461 | [log] [tgz] |
---|---|---|
author | David Munro <davidmunro@google.com> | Wed Jan 22 06:18:48 2020 |
committer | Commit Bot <commit-bot@chromium.org> | Tue Feb 18 20:56:36 2020 |
tree | e5ffd93cc50de160346ef189a4abcad8b22aed00 | |
parent | 78b4c74e8d513c9e4c21fe6bfa4ab0eac79554d1 [diff] |
container-guest-tools: Next try at deflaking gnome-icon-theme. Try installing a known-good package 5 times in a loop with lots of debug info. If they all fail then try installing the package directly via dpkg with absurd levels of logging. BUG=chromium:1044460 TEST=Copied script into a chroot and ran it. Change-Id: Iba4b6dc6fc6b1890d457cf4bfe4fe812fc92769f Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/containers/cros-container-guest-tools/+/2061510 Reviewed-by: David Munro <davidmunro@google.com> Reviewed-by: David Riley <davidriley@chromium.org> Commit-Queue: David Munro <davidmunro@google.com> Tested-by: David Munro <davidmunro@google.com> Auto-Submit: David Munro <davidmunro@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 --host_force_python=py2
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.