[NO-ISSUE] Test case for lowercase Jira ticket names #1964
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.
We had a scenario come up where the release-controller did not take the expected action, on a JIRA ticket, when it was included in a nightly build. After some digging, it turned out that the commit message contained the ticket id in lowercase.
Jira ticket: https://issues.redhat.com/browse/OCPBUGS-48504
PR: openshift/oc-mirror#1008
First Accepted nightly, post merge: https://amd64.ocp.releases.ci.openshift.org/releasestream/4.18.0-0.nightly/release/4.18.0-0.nightly-2025-01-21-015441
Corresponding Release-controller changelog:
This PR adds a test case that illustrates the expected behavior if/when a commit message comes in that doesn't match the expected regex here
The result is that there is no associated reference to a valid Bug.