Small follow-up to close the case. The limit I was experiencing in the build queue was due to the test I was using to stress Jenkins, which was a simple echo. Since the tests were quick to finish and I had lots of requests coming in Jenkins was a bit slow to answer, enough to look like it was waiting for a build to finish...
Now with a sleep of 10 seconds in the test I can stress Jenkins as I wanted with thousands of builds and it still works pretty good (congrats!). Sorry for the trouble! Ronan Le lundi 15 avril 2013 16:42:58 UTC+2, Ronan LE BRUN a écrit : > > Hello, > > I would like to know if there is a known limit to the Build Queue in > Jenkins and how it can be changed/removed if it is the case? > > I intend to use Jenkins as a builder for exhaustive unitary functional > tests. Those tests are created from test campaigns of our Application > Lifecycle Management solution and I had planned to make Jenkins handle the > scheduling, balancing, build and monitoring of those tests. > > However when I try to stress Jenkins with several hundreds builds of a job > with unique parameters I notice an approximative limit of 150 builds in the > Build Queue and the HTTP build requests start to wait for a build to finish > before returning. > > Regards, > Ronan > -- 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 jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
