| commit | f93526dac69ccd8dd626c138b040acff706c2f29 | [log] [tgz] |
|---|---|---|
| author | Fergus Dall <sidereal@google.com> | Sun May 03 23:33:44 2020 |
| committer | Fergus Dall <sidereal@google.com> | Thu May 07 03:13:02 2020 |
| tree | 5fc13dadb187044bf94ef5665c2ce290f787c838 | |
| parent | 6968d7b33455ce2f7b9606a0b49b3c3c08b79df2 [diff] |
kokoro: Allow presubmits to use the real build path Currently the kokoro presubmits use a cut down version of the container build that skips building the cros versions of debian packages. This has caused the presubmits to break since the cros version of apitrace started requiring a later version of libwaffle then is supplied in the debian repos. This change, along with a corresponding change to the internal configs, will make the presubmit flow the same as the normal build, except that it will skip uploading the results to GCS and won't sign anything. The presubmits will cover all combinations of OS versions and archetectures both to ensure full coverage and because this step takes <1/3 of the total build time, so reducing it has fairly marginal gains. BUG=none TEST=untestable! Change-Id: I098d0396effd75be3830d866431c1630627a976e Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/containers/cros-container-guest-tools/+/2176817 Tested-by: Fergus Dall <sidereal@google.com> Reviewed-by: Nicholas Verne <nverne@chromium.org> Reviewed-by: Stephen Barber <smbarber@chromium.org>
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.