|
||||||||
|
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.
I'm interested and this trivial patch works for us with ClearCase for years. We had no option for hooks at server side and ClearCase had no support for atomic commits![]()
But maybe it's possible with ClearCase 8 and CMs are now open for new ideas ![]()
Anyway if hooks are not possible with some SCMs than this is the only way to get SCM plugin with polling mechanism working fast enought and without starting builds in parallel. Why should the system still poll for changes if build is running? It should poll after the build was finished and then build the next changes in one time...