Skip to content

Use oc binary for different platfrom from the release artifacts instead pulling from mirror #1057

Description

@praveenkumar

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.

Activity

  1. cfergeau commented on May 5, 2025

    @cfergeau
    Contributor

    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?

  2. praveenkumar commented on May 6, 2025

    @praveenkumar
    MemberAuthor

    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/ )

    failed job: https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/crc-org_snc/1055/pull-ci-crc-org-snc-master-e2e-microshift/1918206231374204928

  3. self-assigned this
    on May 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions