Any enterprise using Jenkins is very likely to end up having a huge number of Jenkins instances. Most of the discussions about DevOps, in these enterprises, concludes around (a) What can be done about the utilisation of those Jenkins master and slaves, (b) How do we centrally manage all these instances, (c) How can we centrally collect data to understand the overall nature of work happening in development (d) Can we leverage containers to address Jenkins proliferation of this kind, and more. I am happy to say, today, we have something to answer these questions, in the form of *CloudMunch Turbo*. Read more http://www.cloudmunch.com/underneath-cloudmunch-turbo-jenkins-scale-using-kubernetes/
-- 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/4193c27d-4541-4248-81d9-ad4dd259bdf8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
