-
Bug
-
Resolution: Done
-
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.
- blocks
-
STOR-2081 Azure File cross subscription tenant
- New
- is cloned by
-
STOR-2150 Early chore: update openshift/build-machinery-go CI config
- To Do
-
STOR-2157 Early chore: update openshift/build-machinery-go CI config
- To Do
-
STOR-2168 Early chore: update openshift/build-machinery-go CI config
- To Do
-
STOR-2215 Early chore: update openshift/build-machinery-go CI config
- To Do
-
STOR-2242 Early chore: update openshift/build-machinery-go CI config
- To Do
- links to