Skip to content

ocm-ci-fastforward-multiple: fail job when repos skipped for no write access #83832

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

Open
dislbenn wants to merge 1 commit into
base: main
Choose a base branch
from
+10 −0
Open

ocm-ci-fastforward-multiple: fail job when repos skipped for no write access #83832

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
10 changes: 10 additions & 0 deletions ...perator/step-registry/ocm/ci/fastforward-multiple/ocm-ci-fastforward-multiple-commands.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1623,6 +1623,16 @@ if [[ ${#SKIPPED_NO_ACCESS[@]} -gt 0 ]]; then
echo " - ${repo}"
done
echo ""

# A repo skipped for lack of write access is an unexpected access problem
# (revoked token, org membership change, repo transferred/deleted, etc.),
# not an intentional exclusion (those are handled separately via
# SKIPPED_REPOS / SKIP_VERSIONS_PATH and never reach SKIPPED_NO_ACCESS).
# Mark the job as failed so Prow reports failure/error and the Slack
# alert configured in _prowconfig.yaml fires, instead of this condition
# silently persisting across every 2h run.
echo "WARNING: ${#SKIPPED_NO_ACCESS[@]} repo(s) skipped due to no write access; marking job as failed for alerting"
exit_code=$((exit_code | 1))
fi

# List failures if any
Expand Down