|
||||||||||||||||
|
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/d/optout.
Further research, while coding the workaround to prevent the npe, indicated that the cause of this problem is derived from the usage of the multiple scm plugin. A related bug is still open for the multiple scm plugin JENKINS-13160
I've tested the following workaround. Job 1 uses custom workspace workspaces/multiplerepos . Job 2 uses custom workspace workspaces/multiplerepos/repo2
When using a single scm provider per job, all is well.