Maximum number of jenkins jobs/builds

2,163 views
Skip to first unread message

pd

unread,
Feb 4, 2014, 2:37:59 PM2/4/14
to jenkin...@googlegroups.com
Hi,

I have read few responses on the web before posting this question. I am trying to find the 'pristine' documentation that could answer the following 2 questions:

1. What is the maximum number of jobs/builds that can be configured in jenkins before some performance threshold is reached?
2. What is the maximum number of jobs that can be run in jenkins concurrently?

I understand factors such as the underlying hardware (memory, CPU, etc) also govern these guidelines, so it would be helpful if someone could point me to the most accurate jenkins documentation that provides all such guidelines.

Thanks!

Mark Waite

unread,
Feb 4, 2014, 2:51:40 PM2/4/14
to jenkin...@googlegroups.com
I'm afraid your questions are broad enough that they can't reasonably be answered by documentation.

There are Jenkins servers which run hundreds of slave agents and hundreds of jobs concurrently.  A google search for "scaling Jenkins" returned the following presentations which you could review as good sources of information:

http://www.youtube.com/watch?v=8GAAL7T_ozM - Kohsuke Kawaguchi talk on scaling Jenkins
http://di388e0fcqllf.cloudfront.net/whitepapers/7WaysToOptimizeJenkins.pdf - Kohsuke Kawaguchi on some good practices for Jenkins at scale
http://www.slideshare.net/anickelsen/scaling-your-jenkins-ci-pipeline - Scaling Jenkins pipeline by Anders Nickelsen

I believe there were also very useful presentations on scaling Jenkins at previous Jenkins User Conference sessions.

Thanks,
Mark Waite


--
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-de...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.



--
Thanks!
Mark Waite

pd

unread,
Feb 4, 2014, 3:19:00 PM2/4/14
to jenkin...@googlegroups.com
Thank you, kindly, Mark!
Reply all
Reply to author
Forward
0 new messages