fix: skip repos returning 404 instead of failing the matrix job - #21
Merged
Conversation
Signed-off-by: Mario Fahlandt <mfahlandt@pixel-haufen.de>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
When a repository's releases or tags API returns HTTP 404 (e.g.
spiffe/vsecm-sdk-go), the current code callsexit 1, which hard-fails the entire matrix job. This cascades into job failures and cancelled runs for all other repos in that batch.Fix
Detect the
"status":"404"in the error response and treat it as a graceful skip:::warning::so it's visible in the job outputexit 0so the matrix job continues processing other reposApplies to both
generate-sbom.yml(main CNCF jobs) andreusable-generate-sbom.yml(subproject batch jobs), for both the releases and tags API calls.Signed-off-by: Mario Fahlandt mfahlandt@pixel-haufen.de