-
Notifications
You must be signed in to change notification settings - Fork 3.4k
cilium-cli: re-fix GITHUB_WORKFLOW_REF parsing #37707
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.
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
cilium-cli: re-fix GITHUB_WORKFLOW_REF parsing #37707
Conversation
af9ac19 introduced an issue where the cilium-cli connectivity check could panic when GITHUB_WORKFLOW_REF was not set as expected. This commit changes the GITHUB_WORKFLOW_REF parsing logic using a regexp capture to extract the workflow name from GITHUB_WORKFLOW_REF and check whether the match was successful. Reported-by: Martynas Pumputis <martynas@isovalent.com> Signed-off-by: Alexandre Perrin <alex@isovalent.com>
ac38918
to
5d03fab
Compare
/test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the fix. Works as expected.
We're even lucky enough to get a random failure in ci-clustermesh that demonstrates that this fixes the issue that was reported, as in the case where GITHUB_WORKFLOW_REF is unspecified it just ignores the workflow attribution rather than crashing: https://github.com/cilium/cilium/actions/runs/13392927898/job/37404692001#step:54:463 🎉 |
Hit #37718 |
af9ac19 introduced an issue where the cilium-cli connectivity check could panic when
GITHUB_WORKFLOW_REF
was not set as expected.This commit changes the
GITHUB_WORKFLOW_REF
parsing logic using a regexp capture to extract the workflow name fromGITHUB_WORKFLOW_REF
and check whether the match was successful.Fix #37705