Dear All The way in which Jenkins manages tasks and machines is very powerful. We are thinking about moving our python written system to distribute builds across server farm in to the Jenkins.
The challenge that I recognize will be a number of parallel tasks that needs to be handle by Jenkins. Basically I create project which based on dependency triggers the downstream project with using of groovy system scripts and *schedule2(Task, int, List) <http://javadoc.jenkins-ci.org/hudson/model/Queue.html#schedule2%28hudson.model.Queue.Task,%20int,%20java.util.List%29>.* Since the number of downstream builds of the same project (with different parameter) may achieve range (200-1000) I recognize performance issue. It's really hard to say if the bottle neck is coming from: * the bad design of one of the plugin installed in the chain or * basically the Jenkins is not the right tool for such a scale of parallel task due to its' overhead. I debug a bit with visualvm to found a bottle neck, however couldn't found any interesting. Anyone is having experience with such a large build queue. Could you share hints/best practice? Best regards, Tomasz Majchrowski. -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/bb6d5973-f2e1-4326-843e-5a20af42443a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
