|
||||||||
|
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/d/optout.

We have a problem and the described behavior seems to be responsible for that:
We have a SVN, named "http://hostname/svn/BLACK" and another one, which is called "http://hostname/svn/BLACKOPS". If we trigger jenkins via svn-hook to start a defined projekt which is looking for a subprojekt at the "BLACKOPS" repository, the following appears at the logger (configured for hudson.scm.SubversionRepositoryStatus):