Skip to content

USHIFT-1359: Rebase: write cluster registry credentials to custom path #1954

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
openshift-merge-robot merged 1 commit into from
Jun 23, 2023
Merged

USHIFT-1359: Rebase: write cluster registry credentials to custom path #1954

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 5 additions & 3 deletions scripts/auto-rebase/rebase_job_entrypoint.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,9 +17,11 @@ cp /secrets/ci-pull-secret/.dockercfg "$HOME/.pull-secret.json" || {
echo "WARN: Could not copy registry secret file"
}

oc registry login
release_amd64="$(oc image info $OPENSHIFT_RELEASE_IMAGE -o json | jq -r '.config.config.Labels."io.openshift.release"')"
release_arm64="$(oc image info $OPENSHIFT_RELEASE_IMAGE_ARM -o json | jq -r '.config.config.Labels."io.openshift.release"')"
# log in into cluster's registry
oc registry login --to=/tmp/registry.json
release_amd64="$(oc image info --registry-config=/tmp/registry.json $OPENSHIFT_RELEASE_IMAGE -o json | jq -r '.config.config.Labels."io.openshift.release"')"
release_arm64="$(oc image info --registry-config=/tmp/registry.json $OPENSHIFT_RELEASE_IMAGE_ARM -o json | jq -r '.config.config.Labels."io.openshift.release"')"

# LVMS is not tracked in the OCP release image. Instead, rely on the latest X.Y stream as the release image.
# LVMS also does not cut nightly releases where ocp-release does. This means that latest ocp-releases' y-stream
# can increment independently from LVMS, and will usually be 1 y-stream ahead of LVMS in-between OCP releases.
Expand Down