Support needed for Jenkins Server Specification

[MANIKANDAN BABU]

Hi,

We are in process of implementing the Jenkins.

 Recommendation needed  for Jenkins server specification handling 200 slaves, with ~100 build steps.

Thanks in Advance

Manikandan

[Artur Szostak]

I think the biggest dependency will be on the number and complexity of jobs.
My experience has shown more or less a linear increase in the amount of Memory and I/O performance needed as a function of the number of jobs. One has to count the sub-jobs if dealing with a MatrixJob etc.
As for disk space, ignoring I/O performance, just thinking about the size of the volume, that really depends on how much history you want to keep and how big the build logs and artifacts get per build.

Best regards.

Artur
________________________________________
From: jenkins...@googlegroups.com <jenkins...@googlegroups.com> on behalf of MANIKANDAN BABU <mkmecha...@gmail.com>
Sent: 01 September 2017 10:49:54
To: Jenkins Users
Subject: Support needed for Jenkins Server Specification

--
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-use...@googlegroups.com<mailto:jenkinsci-use...@googlegroups.com>.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/74081fa0-dc76-4f04-a9a3-17f2d611406d%40googlegroups.com<https://groups.google.com/d/msgid/jenkinsci-users/74081fa0-dc76-4f04-a9a3-17f2d611406d%40googlegroups.com?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.google.com/d/optout.

[MANIKANDAN BABU]

Hi Artur,

Thanks for your suggestion.

Manikandan

On Friday, September 1, 2017 at 6:43:21 PM UTC+5:30, Artur Szostak wrote:

I think the biggest dependency will be on the number and complexity of jobs.
My experience has shown more or less a linear increase in the amount of Memory and I/O performance needed as a function of the number of jobs. One has to count the sub-jobs if dealing with a MatrixJob etc.
As for disk space, ignoring I/O performance, just thinking about the size of the volume, that really depends on how much history you want to keep and how big the build logs and artifacts get per build.

Best regards.

Artur
________________________________________
From: jenkins...@googlegroups.com <jenkins...@googlegroups.com> on behalf of MANIKANDAN BABU <mkmecha...@gmail.com>
Sent: 01 September 2017 10:49:54
To: Jenkins Users
Subject: Support needed for Jenkins Server Specification

Hi,

We are in process of implementing the Jenkins.

 Recommendation needed  for Jenkins server specification handling 200 slaves, with ~100 build steps.


Thanks in Advance
Manikandan





--
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-use...@googlegroups.com<mailto:jenkinsci-users+unsubscribe@googlegroups.com>.