hack/build: Pin to RHCOS 47.212 and quay.io/openshift-release-dev/ocp-release:4.0.0-6 #918
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
openshift-ci-robot
added
the
size/M
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: wking The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-ci-robot
added
the
approved
wking
force-pushed
the
version-0.7.0-pins
branch
from
00c6f45 to
53e7fce
Compare
Covering 5813f61 (Merge pull request openshift#745 from wking/s3-vpc-endpoint, 2018-12-13) through 874876e (Merge pull request openshift#711 from staebler/improve_input_validation, 2018-12-14).
…-release:4.0.0-6 That's the latest RHCOS release: $ curl -s https://releases-rhcos.svc.ci.openshift.org/storage/releases/maipo/builds.json | jq '{latest: .builds[0], timestamp}' { "latest": "47.212", "timestamp": "2018-12-14T23:43:06Z" } And Clayton just pushed 4.0.0-0.alpha-2018-12-13-230701 to quay.io/openshift-release-dev/ocp-release:4.0.0-6. 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). 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.
wking
force-pushed
the
version-0.7.0-pins
branch
from
53e7fce to
17ffd16
Compare
/retest |
|
All green here, and I've tagged this commit as v0.7.0. /close |
|
@wking: Closed this PR. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
DO NOT MERGE!
Builds on the still-in-flight #757, but I'm pushing this now to get CI coverage.
That's the latest RHCOS release:
And @smarterclayton just pushed 4.0.0-0.alpha-2018-12-13-230701 to quay.io/openshift-release-dev/ocp-release:4.0.0-6.
Renaming
OPENSHIFT_INSTALL_RELEASE_IMAGE_OVERRIDEgets us CI testing of the pinned release despite openshift/release@60007df2 (openshift/release#1793).I'd initially expected to export the pinning environment variables in
release.sh, but I've put them inbuild.shhere because our continuous integration tests use build.sh directly and don't go throughrelease.sh.