Interesting. No denying what you propose would not be useful. But maybe at least for Git you could consider using a post receive hook to lower the load on your server and not have this kind of issue you're currently having. My 2 cents. Le 5 oct. 2013 17:10, "Sascha Vogt" <[email protected]> a écrit :
> Hi, > > Yes, I know that, but if you notify a new commit a new "poll task" gets > put in the polling queue. Where it is queued behind a plethora of CVS > polling tasks (which on our system sometimes takes up to 10 minutes until > all the CVS tasks are done and THEN the Git job can finally be executed). > > That's what I'm shooting at with using a different queue per SCM. > > Greetings > -Sascha- > > Am 03.10.13 20:13, schrieb Richard Bywater: > >> Re Git, you only need SCM polling ticked - you don't need to actually >> have a value in the polling field. >> >> Not sure if that helps but thought I'd mention it. >> >> Richard >> >> On Thursday, September 26, 2013, Sascha Vogt wrote: >> >> Hi all, >> >> We are currently in the unfortunate situation that we have multiple >> SCM >> types (CVS, SVN, Git) and use polling for them. Now, our CVS server is >> quite slow and to restrict the load, we have to put a limit on the >> concurrent pollings. While the other SCMs are much faster (and with >> Git >> we even push, but pushing means a custom poll task is added to the >> polling queue), CVS tasks block the queue. >> >> Would it make sense to have a queue per SCM type? Would this be a >> welcomed contribution? Or should this be a new configuration option >> (flag: restrict per type or overall)? >> >> For Git we're using the URL >> /git/notifyCommit?url=$url/**git/$repository.name >> <http://repository.name> - would it be possible >> to bypass the polling queue only for Git? That would already help a >> bit. >> >> Greetings >> -Sascha- >> >> -- >> You received this message because you are subscribed to the Google >> Groups "Jenkins Developers" group. >> To unsubscribe from this group and stop receiving emails from it, >> send an email to >> jenkinsci-dev+unsubscribe@**googlegroups.com<jenkinsci-dev%[email protected]> >> <javascript:;>. >> For more options, visit >> https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out> >> . >> >> -- >> You received this message because you are subscribed to the Google >> Groups "Jenkins Developers" group. >> To unsubscribe from this group and stop receiving emails from it, send >> an email to >> jenkinsci-dev+unsubscribe@**googlegroups.com<jenkinsci-dev%[email protected]> >> . >> For more options, visit >> https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out> >> . >> > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to > jenkinsci-dev+unsubscribe@**googlegroups.com<jenkinsci-dev%[email protected]> > . > For more options, visit > https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out> > . > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" 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/groups/opt_out.
