| commit | 457f9d6cbebe716625cf148c28ad08320fdf5f1f | [log] [tgz] |
|---|---|---|
| author | James Ye <jamesye@google.com> | Fri Jan 06 17:35:11 2023 +1100 |
| committer | Chromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Jan 10 04:38:29 2023 +0000 |
| tree | f88894d9ca79e23767a18f085289f76665c7ec5b | |
| parent | 1cf64a7071398a8a8ab535bdd510e89f63f0f570 [diff] |
kokoro: Print instance information during build To aid debugging of build failures, print some useful information from the metadata service in each build. BUG=b:263327529 TEST=kokoro Change-Id: Ifc42ddbf2b23e35f4359df0b0f63c79edfa7f22d Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/containers/cros-container-guest-tools/+/4145288 Reviewed-by: David Munro <davidmunro@google.com> Tested-by: kokoro <noreply+kokoro@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.