|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
I recommend a separate bug report for those SCM systems which show the problem. As far as I can tell from comments by Cletus D'Souza, the PTC Integrity SCM plugin is still maintained by him and its bugs are still tracked in the Jenkins Jira instance.
You said in your first posting that "it seems more general". I disagree. I don't think it is more general. I think the cases which cause the problem are specific to each plugin. That was certainly the case for the example which was reported against the Git plugin. Changes in core Jenkins or in the scm-api plugin would not have fixed the issue in the git plugin. I suspect it is the same for your PTC Integrity case.