|
||||||||
|
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 fell into that pit, too.
It seems to be intependent if the CS is read from file or defined static in the Jenkins job.
When Jenkins sets the config-spec on Windows platforms it obviously converts slashes to backslashes,
which results in the mentioned CS mismatch (and e.g. triggers SCM polled builds).
I fixed it by changing the CS definition in Jenkins to use backslashes.
Accepting both by the plugin would be nice. However, at least in our environments VOBs
are located below the root directory on Windows and below /vobs on Unix.
So config-specs at least for us are platform specific.