JIRA-Plugin: Problem with SVN-Externals

[Dieter Guthmann]

Hi,

we use Jenkins-CI with a SVN post commit hook script as build trigger.
Our SVN repositories uses heavily "SVN externals" for 'importing' independent modules into other repositories. So a build can be triggered by a commit onto the original project-repository or by a commit at one of the 'imported' repositories.
That configuration does works almost perfectly in Jenkins - builds are triggered in both cases.

We've now activated den JIRA-Plugin to connect our JIRA-Instance (v6.4.11). The comment-function basically works and looks really helpful - in svn repositories which no SVN-externals are used, the JIRA-comment-function works great.
In projects WITH externals the plugin often creates numerous comments per commit. Thats ok, when a commit affects more than one jenkins-job/svn-project-repository if e.g. some work in a 'imported' module was done:
SUCCESS: integrated in PROJECT A
<svn commit comment>
- files
SUCCESS: integrated in PROJECT B
<svn commit comment>
- files

But sometimes ONE JIRA-Issue is commented by the JIRA-Plugin for multiple builds out of the same Jenkins-job. e.g.
SUCCESS: integrated in PROJECT A #2366
SUCCESS: integrated in PROJECT A #2367

The commit-comment of Build 2367 doesn't contain any JIRA Issue-ID (commit-comment was empty also) or sometimes it contained a different JIRA Issue-ID (can't see a pattern at this time).
That problem does not occur on every build. It seems that these problems only affects jobs with subversion-repositories, which has 'svn-externals' referenced.

Thanks in Advance.

Rgds.
Dieter

[d.gut...@gmx.net]

Additional Information:

We use currently Jenkins vers. 1.509.4 with the "Jenkins JIRA plugin" V. 1.39