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 - 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 [email protected] <javascript:;>. > For more options, visit 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.
