Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

hack/build: Pin to RHCOS 47.212 and quay.io/openshift-release-dev/ocp-release:4.0.0-6 #918

Closed
wants to merge 2 commits into from

Commits on Dec 15, 2018

  1. CHANGELOG: Document changes since 5813f61

    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).
    wking committed Dec 15, 2018
    Configuration menu
    Copy the full SHA
    04dda38 View commit details
    Browse the repository at this point in the history
  2. hack/build: Pin to RHCOS 47.212 and quay.io/openshift-release-dev/ocp…

    …-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 committed Dec 15, 2018
    Configuration menu
    Copy the full SHA
    17ffd16 View commit details
    Browse the repository at this point in the history