On Wed, Oct 5, 2016 at 9:29 AM <[email protected]> wrote: > Our git server is set up to notify our jenkins instance whenever a commit > was received by using cURL by saying checking poll SCM for changes and > adding an empty schedule. As our developer count has grown we've noticed a > slow increase in backlog, and it seems to be that while there is a build > the git plugin won't be poll for changes. When the build finishes it'll > poll fine. > > It's set up to only build from branches with a certain prefix - is that > what's preventing concurrent polling? > > Unfortunately, no, building branches with a certain prefix is not what blocks git plugin polling (on a specific job) while the job is running. https://issues.jenkins-ci.org/browse/JENKINS-25304 indicates that if there is a wildcard in the branch to be built, then polling will block on that job until the job completes.
Mark Waite > Patrick Rose > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/94e91126-b500-4de6-9a60-79bce3e20e9e%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-users/94e91126-b500-4de6-9a60-79bce3e20e9e%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtGuH1-CUN7gKekfsvW6_gxgtTnx2gxfHUtop7_evctTmw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
