Other question : What do you use to launch Jenkins ? Currently, we are using Winstone. Is this the best way?
2012/9/26 mpapo - Michaël Pailloncy <mpapo....@gmail.com> > Hi all, > > Currently, we manage near 250 jobs related to several java projects and > several teams in our company. > > Our CI architecture characteristics : > - a Jenkins master on AIX 5.3 with 8 processors and 10 GB of RAM > - 3 RHEL slaves with 2 processors and 4 GB of RAM > - 2 Windows slaves with 1 processors and 2 GB of RAM > > We arrive sometimes has limitations with Jenkins. Especially during > releases. > > Due to an increase of job number in our Jenkins in my company, we want to > change our architecture to meet our needs. We are going to manage near 500 > jobs. > We want to switch the master on a RHEL OS (our new main target platform) > and add an AIX slave for projects that need this platform. > > Here are our thoughts : > > - Do you think it would be interesting to have a master only used to > monitor the jobs (0 executor, all builds are delegate to slaves) ? > > This could be interesting to have a more stable and more reliable master. > > - On the other hand, do you think it could be interesting to use multiple > masters ? One for each team for example ? > > This could be nice to have a more specialized master per team but I guess > it must increase the maintenance time. > > > > I need feedbacks from the community to choose the best architecture : > How many jobs do you manage ? > What are the characteristics of your architecture ? (number of slaves, of > master ??) > Would you prefer to use a slave with large capacity, or more with > capacities smaller? > > > Thanks in advance from any help and feeback ! > > Michaël Pailloncy > > >
