|
||||||||
|
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.
Same issue (Jenkins 1.510 and ClearCase 1.3.14).
Maybe you can confirm, but it seems to be related to using different platforms for master and slave:
Master: Unix/Solaris
Slave: Windows
or
Master: Windows
Slave: Unix/Linux
ClearCase polling log looks good but "No changes" is reported.
I have the impression that is related to the mix of slashes and backslashes for the polling output
(e.g. on Windows using backslashes) and comparing them with the polling rules (e.g. on Unix master).
It does not help if I define the polling rules with backslashes in order to match the Windows slave polling output.
In order to confirm this theory I moved a polling job from Windows to Unix and - now it works!
The Unix SCM polling job triggers then the Windows build job.
So I would say (and also found other, older quotes confirming that): SCM polling needs to run on master
Of course I voted here to get this fixed and fianlly working transparently.