| commit | dceb3e40fe8aec34665f91f3167af33ba2ed5f2a | [log] [tgz] |
|---|---|---|
| author | Mike Frysinger <vapier@chromium.org> | Tue Sep 13 05:35:25 2022 -0400 |
| committer | Chromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Sep 14 16:22:51 2022 +0000 |
| tree | d38ff0f5bc30e5abb60ffc6c06bfcdc80184f89c | |
| parent | f0ea2b21ec12092cbac8e66de73827d651eb68ca [diff] |
Update license boilerplate text in source code files Normally we don't do this, but enough changes have accumulated that we're doing a tree-wide one-off update of the name & style. BUG=chromium:1098010 TEST=`repo upload` works Change-Id: Ia9258e2bb14955402ac7365c09f293fff59bd3b6 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/containers/cros-container-guest-tools/+/3891623 Commit-Queue: Mike Frysinger <vapier@chromium.org> Tested-by: kokoro <noreply+kokoro@google.com> Tested-by: Mike Frysinger <vapier@chromium.org> Reviewed-by: 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
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.