| commit | 3cbe00b4bc4b4ff6dfc14409a92afb4829b25559 | [log] [tgz] |
|---|---|---|
| author | James Ye <jamesye@google.com> | Wed Feb 23 06:07:09 2022 |
| committer | Commit Bot <commit-bot@chromium.org> | Fri Feb 25 06:26:55 2022 |
| tree | 350d6749e7e1bc7c0c072c39d4f9981dc7e1d956 | |
| parent | 34478a9fcff675c9299c022083472cc6078c1149 [diff] |
*.sh: use -o pipefail This makes pipelines containing failed commands exit the shell when used in combination with `-e`. As an example, `curl ... | gpg --dearmor | tee` may fail to execute correctly due to an incorrect server response. While gpg has non-zero exit, it is masked by the successful tee exit. The error is only revealed when `apt update` fails to verify GPG signatures, but we want to fail as soon as possible. Change-Id: I5d78a622eb8b79ee198567a6e60894444f67d4b4 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/containers/cros-container-guest-tools/+/3482644 Reviewed-by: David Munro <davidmunro@google.com> Tested-by: kokoro <noreply+kokoro@google.com> Reviewed-by: Fergus Dall <sidereal@google.com> Commit-Queue: James Ye <jamesye@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.