|
||||||||
|
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.
To ensure uniqueness, the plugin scans through all instances of the IntegritySCM plugin when a new job is created. Basically all jobs that use the Integrity plugin. Hence as you create a new job the old job data (from different existing jobs) have to be loaded. Due to the nature of changes in this plugin, it couldn't be backward compatible. So, we get the null pointer exception.
No, it is not OK to use environment variables for the Configuration Name. The Configuration Name needs to be unique as some folks want to use this plugin inside of the Multiple SCM plugin.