-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Fixed
-
Component/s: jira-plugin
-
Labels:None
-
Environment:Platform: All, OS: All
-
Similar Issues:
If we have a JIRA project called APP, cases referenced like APP-101 are
detected, but not app-101, even though JIRA happily accepts any case including
mix and match. The regex should probably be case insensitive.
made 'recent changes' also case insensitive in 1.18
We already have some unwanted build failures because the matching was case-insensitive in some places (granted, they won't fail anymore since JENKINS-3046). Typically, when using the maven release plugin, it will have an scm log message along the lines of "preparing release of projectname-2.3.4" - the jira issue matching see this and attempts to log a comment in a jira issue called projectname-2, which is usually completely irrelevant or unexistant.
The plugin shouldn't match any patterns like 'projectname-2.3.4', because of the dots between the numbers. If it does, please open a new issue for it.
It did match (up to projectname-2), but since JENKINS-6043, this can now be worked around by customizing the regex.
(as a side note, sending the keys uppercased to jira is pointless, it will recognize them independently of the case)
Code changed in hudson
User: : kutzi
Path:
trunk/hudson/plugins/jira/src/main/java/hudson/plugins/jira/JiraChangeLogAnnotator.java
trunk/hudson/plugins/jira/src/main/java/hudson/plugins/jira/JiraSession.java
trunk/hudson/plugins/jira/src/main/java/hudson/plugins/jira/JiraSite.java
trunk/hudson/plugins/jira/src/test/java/hudson/plugins/jira/JiraChangeLogAnnotatorTest.java
http://fisheye4.cenqua.com/changelog/hudson/?cs=25741
Log:
JENKINS-4132case-insensitive matching of JIRA ids in the ChangeLogAnnotator