|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
The problem description and the stack trace all seem to indicate a problem with the specific Subversion SCM plugin.
In this case, it appears the Subversion plugin is sometimes throwing an exception. I think the core is behaving correctly that if polling throws an exception, it assumes there is a change, rather than assuming no change on an exception.
I think that if a plugin independent component calls a plugin specific component to check for changes, and that plugin specific component throws an exception, I'd rather have the plugin independent portion assume there was a change, rather than have it assume that an exception meant no change.
I think this specific bug report is about Subversion and needs to be assigned to the Subversion plugin, rather than being assigned to scm-api, since I think the scm-api is behaving correctly in this case.