Do you only have the two teams? How do you manage the multiple nodes? Also how many users do you have using Jenkins?
On Thursday, July 28, 2016 at 12:34:02 PM UTC-7, R Tyler Croy wrote: > > (replies inline) > > On Thu, 28 Jul 2016, rqui wrote: > > > I am seeking some advice/tips. Our group is experiencing fast growth and > > changes and I am trying to architect a solution for managing it. > > > > We currently have a single master handling various types of jobs: ci, > > nightlies, releases, personal dev builds, etc. > > > > Using OSS, does anyone have experience in handling several masters for > > handling the different functions: CI, Releases, DEV? > > > > Or, do you continue to use a single Jenkins master? > > > > Any help, advice or tips would be greatly appreciated. > > > I will assume that you are not running jobs on the master, if you are, > that's > the first step to growing is removing all workloads from the master and > delegating them to agents. > > > For most use-cases I have either worked with or seen, delegating work to > the > agents and then putting a beefy machine in place for the master (fast disk > I/O) > is sufficient to grow into the many hundreds of jobs/thousands of builds > per > day. > > > If you're growing past that, I suggest splitting into multiple independent > masters based on the workloads associated with them. For example, I might > break > out the jobs for the "mobile team" to a new master infrastructure since > they > have Android/iOS build requirements and let the "server" team stick to > another > master with a number of Linux agents. This has the added benefit of > separating > concerns, plugins and access control based on logic separations inside > your > organization. > > > > > Hope that helps point you in the right direction. > > > > - R. Tyler Croy > > ------------------------------------------------------ > Code: <https://github.com/rtyler> > Chatter: <https://twitter.com/agentdero> > > % gpg --keyserver keys.gnupg.net --recv-key 3F51E16F > ------------------------------------------------------ > -- 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/28e42f8a-d89b-4f8b-95be-983aedae21dc%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
