|author||Fergus Dall <firstname.lastname@example.org>||Mon Jan 18 12:03:36 2021|
|committer||Commit Bot <email@example.com>||Tue Jan 19 08:35:09 2021|
container-guest-tools: Deal with gsutil gsutil cp -r has semantics that depend on whether the target directory already exists or not. If it does, the source directory will be created under the target, otherwise the *contents* of the source directory are copied directly under the (newly created) target. Make sure we always target a directory that (shouldn't) exist by including the build number in the target path. BUG=none TEST=Ran script Disallow-Recycled-Builds: test-failures Change-Id: Idd362a72e8d6533142613d8f08b77430f63fbd89 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/containers/cros-container-guest-tools/+/2636034 Reviewed-by: Nicholas Verne <firstname.lastname@example.org> Tested-by: kokoro <email@example.com> Commit-Queue: Fergus Dall <firstname.lastname@example.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 --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.