| commit | 55114e7d17b4df542d5fb4de81d1a70905ccd459 | [log] [tgz] |
|---|---|---|
| author | David Riley <davidriley@chromium.org> | Wed Nov 13 23:38:40 2019 |
| committer | Commit Bot <commit-bot@chromium.org> | Thu Nov 14 01:31:41 2019 |
| tree | efd19d33fcae1d26b2d5bbde81dc6af3abad1d44 | |
| parent | 67752476528a825627100eda27d16b97c27a04f5 [diff] |
common: Fix typo with docker image loading. The typo shouldn't have had any effect -- the kokoro instance should be invoking this code exactly once on a fresh device each time, so we'd expect the load to occur exactly once which is what is currently happening. BUG=None TEST=None Change-Id: I5d274ca5489984898ce4a8855a6afde54a488e87 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/containers/cros-container-guest-tools/+/1915090 Reviewed-by: Benjamin Gordon <bmgordon@chromium.org> Commit-Queue: David Riley <davidriley@chromium.org> Tested-by: David Riley <davidriley@chromium.org> Tested-by: kokoro <noreply+kokoro@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.