1
0
mirror of https://github.com/openshift/installer.git synced 2026-02-05 15:47:14 +01:00
Files
installer/hack
W. Trevor King 357bd71bc7 hack/build: Pin to RHCOS 47.249 and quay.io/openshift-release-dev/ocp-release:4.0.0-0.1
Recycling the RHCOS build from 76f91bdf (hack/build: Bump RHCOS from
47.245 to 47.249, 2019-01-07, #1009, v0.9.1).

Clayton pushed 4.0-art-latest-2019-01-15-010905 to
quay.io/openshift-release-dev/ocp-release:4.0.0-0.1 for 0.10.0, and
we've had stability issues in master since then, so we're cutting this
release without an update-payload bump.

Renaming OPENSHIFT_INSTALL_RELEASE_IMAGE_OVERRIDE gets us CI testing
of the pinned release despite openshift/release@60007df2 (Use
RELEASE_IMAGE_LATEST for CVO payload, 2018-10-03,
openshift/release#1793).

Also comment out regions which this particular RHCOS build wasn't
pushed to, leaving only:

  $ curl -s https://releases-rhcos.svc.ci.openshift.org/storage/releases/maipo/47.246/meta.json | jq -r '.amis[] | .name'
  ap-northeast-1
  ap-northeast-2
  ap-south-1
  ap-southeast-1
  ap-southeast-2
  ca-central-1
  eu-central-1
  eu-west-1
  eu-west-2
  eu-west-3
  sa-east-1
  us-east-1
  us-east-2
  us-west-1
  us-west-2

I'd initially expected to export the pinning environment variables in
release.sh, but I've put them in build.sh here because our continuous
integration tests use build.sh directly and don't go through
release.sh.
2019-01-22 12:28:31 -08:00
..
2018-09-11 15:19:08 -07:00
2018-12-20 14:08:04 -05:00
2018-09-11 15:19:08 -07:00
2018-09-11 15:19:08 -07:00
2018-11-22 09:50:07 -08:00
2018-09-11 15:19:08 -07:00