You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Use oc binary for different platfrom from the release artifacts instead pulling from mirror #1057
Sometime there is nightly builds which doesn't have corresponding oc binary available to mirror and CI fails on that step, better to use the release artifact to get the oc binary for different platform instead relying on the mirror.
Sometime there is nightly builds which doesn't have corresponding oc binary available to mirror
Is this something that is expected and that we need to deal with, or does this indicate an issue with openshift build processes which could be fixed at some point?
Sometime there is nightly builds which doesn't have corresponding oc binary available to mirror
Is this something that is expected and that we need to deal with, or does this indicate an issue with openshift build processes which could be fixed at some point?
This is something we need to deal with, in microshift context they don't release the oc binary for nightly so we might need to get it from a well known url ( like for master branch and release branch (until not published) it would be https://mirror.openshift.com/pub/openshift-v4/clients/ocp-dev-preview/latest/ )
Sometime there is nightly builds which doesn't have corresponding oc binary available to mirror and CI fails on that step, better to use the release artifact to get the oc binary for different platform instead relying on the mirror.