Uploaded image for project: 'OpenShift Storage'
  1. OpenShift Storage
  2. STOR-2080

Early chore: update openshift/build-machinery-go CI config

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • None

      After branching of a new OCP release, create CI jobs for openshift/build-machinery-go for that release.

      Typically, something like this.

      We use commitchecker, built from openshift/build-machinery-go, in our CI jobs. Its image lives in `ci` namespace and thus DPTP team won't update -master.yaml for a new release and won't create a new release-4.y.yaml. We must do it manually. And it's us, because nobody else cares.

            rhn-engineering-jsafrane Jan Safranek
            rhn-engineering-jsafrane Jan Safranek
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: