commit | 4e623bdb760152a6e3748215136b8cfe1cc9c36c | [log] [tgz] |
---|---|---|
author | Fergus Dall <sidereal@google.com> | Mon Dec 07 11:31:10 2020 +1100 |
committer | Commit Bot <commit-bot@chromium.org> | Mon Dec 07 08:13:05 2020 +0000 |
tree | b956f16a0d9640f224e855e23f3f5d4984d926a4 | |
parent | b27ac97167b26a3d4215782ccec77452a18069e9 [diff] |
Pass --dedupe to upload_symbols This avoids uploading debug symbols which have already been uploaded, dramatically speeding up the upload. In testing, only 40-50 symbol files out of 1,250 needed uploaded, probably because our new release builder is uploading a mostly identical set. BUG=none TEST=ran script Disallow-Recycled-Builds: test-failures Change-Id: I55c1f7f34cb6197d9b8933c87b4f974c6d0f899a Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/containers/cros-container-guest-tools/+/2574579 Reviewed-by: David Munro <davidmunro@google.com> Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: 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 --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.