commit | fb9c562743f275d5cc0a603bcc50500b2992cc61 | [log] [tgz] |
---|---|---|
author | Fergus Dall <sidereal@google.com> | Tue Jun 16 12:28:28 2020 +1000 |
committer | Commit Bot <commit-bot@chromium.org> | Wed Jun 17 00:20:04 2020 +0000 |
tree | 1f2e11dc67d35e4f8d786b1ec8215d9b55a94a99 | |
parent | a8f90c38766e13c63424ee12fd97821068927a32 [diff] |
mesa: stretch: Fix usage of --git-upstream-tree This currently points to origin/master instead of 19.2, the branch actually being built from. This causes gbp buildpackage to generate excessivly large diffs, and recently this broke outright as upstream modifying a binary file which the diff format cannot represent. Since we don't actually care what the diffbase is, set it to ${MESA_BRANCH} so it will always just be an empty diff. BUG=none TEST=Built mesa locally Change-Id: I562f5a396962354923c118ac18a484c352a23416 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/containers/cros-container-guest-tools/+/2245846 Reviewed-by: Stephen Barber <smbarber@chromium.org> Reviewed-by: David Munro <davidmunro@google.com> Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: Fergus Dall <sidereal@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.