We need to check both OOD and old provisioning jobs which OCP build they use. Nightly builds will no longer be moved to dev-preview locations

A/C: All of our OCP provisioning jobs work fine with the new locations of the nightly OCP builds. All jobs should work like before, no breakages.

For more context, below is the content of the email thread that announces this change:

===========================================================================

 
tl;dr External testing should focus on EC and RC builds mirrored to quay.io and dev-preview locations[1]. Nightlies are no longer mirrored to quay.io or preserved indefinitely, Please verify that you’re testing with fresh builds, we’ve been made aware of teams who were watching odd mirror locations which are no longer updated.

Since OCP 4.11 we’ve been delivering Engineering Candidate (EC) and, after branching, Release Candidate (RC) builds on a sprintly and weekly basis respectively. These builds are mirrored publicly and suitable for external feature verification as well as early regression identification. We’re working toward delivering release notes and raising the bar on overall coherency of these builds so that less time is wasted. The overall hope is to build more effective feedback loops through focused attention on 3-4 EC and 4-8 RC builds per minor release.

A previously unannounced change associated with this effort was that nightly builds which were mirrored publicly are no longer mirrored to dev-preview locations. While these builds are still produced and made available to anyone who can pull from registry.ci.openshift.org they are not preserved indefinitely or mirrored to quay.io where anyone with an OpenShift pull secret could previously consume them. See linked documentation for how to pull images from registry.ci.openshift.org[2]

We recognize that some teams depended on this, either intentionally or because their use was simply easier to consume. However, after gathering feedback in FDN-177[3] we intend to continue the current development branch delivery patterns established as part of 4.Next. We’d like to ask teams, particularly those who coordinate on feature testing with external parties, to shift toward testing of EC and RC builds. For internal teams who require rapid feedback loops and can continue consuming builds from registry.ci.openshift.com feel free to do so.

There is no plan to change our internal verification processes. We will continue to verify fixes internally on nightly builds and then backport the fixes. We will not require external verification on an EC prior to backporting a fix as this would substantially slow our ability to deliver backported fixes to z-streams. If QE becomes blocked and requires external verification we’re building a process for requesting one-off nightlies to be mirrored publicly in ART-4089[4], the hope being that this process is rarely necessary.

1 - [+https://mirror.openshift.com/pub/openshift-v4/clients/ocp-dev-preview/latest/+]

2 - https://docs.ci.openshift.org/docs/how-tos/use-registries-in-build-farm/#common-questions

3 - +https://issues.redhat.com/browse/FDN-177+

4 - +https://issues.redhat.com/browse/ART-4089+

Scott