[
https://issues.jenkins-ci.org/browse/JENKINS-7423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159875#comment-159875
]
abayer commented on JENKINS-7423:
---------------------------------
This is valid - the git plugin requires access to the workspace for polling,
and so can't poll for changes while a build is running. Workarounds include
changing to using post-receive hooks, having a parent job that does nothing but
poll and if it finds changes, kick off the real build, etc.
> Git polling doesn't execute concurrent builds if necessary
> ----------------------------------------------------------
>
> Key: JENKINS-7423
> URL: https://issues.jenkins-ci.org/browse/JENKINS-7423
> Project: Jenkins
> Issue Type: Bug
> Components: git
> Affects Versions: current
> Environment: windows xp
> Reporter: anonymousultimo
> Fix For: current
>
> Attachments: screenshot-1.jpg
>
>
> We would like to make use off git polling more than it does now.
> We've selected to poll every five minutes for changes because we commit a lot.
> Our projects take approximately 50 to 70 minutes to build and we've got over
> a dozen machines that can build for us.
> What we would like is that every five minutes a build would start if there
> are changes, but this doesn't happen. We've selected Execute concurrent
> builds if necessary (beta) but git doesn't start the actual polling again
> after the build is done.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
