That brings up another point...how does handling growth and implementing cloud (private or public) play a part as well?
On Thursday, July 28, 2016 at 9:53:35 AM UTC-7, 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. > > -- 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/14c4d594-c15c-4bf9-adc7-176fbeed2064%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
