Jenkins World 2017

This session will describe how some companies used automated Jenkins’ best practices to remove anti-patterns, avoid known issues, have a healthy and stable Jenkins ecosystem.

The challenge to deliver a heterogeneous and distributed Jenkins ecosystem around the world with a massive number of Jenkins users is great. It becomes even greater when the portfolio of tasks within Jenkins encompasses not just continuous integration, but a number of other automation tasks as well (for example, batch tasks to run DWH processes, end-to-end system tests, administrative tasks). However, defining a set of Jenkins best practices will help teams to reduce their potential issues and get the benefits from others, even when those teams are coming from different backgrounds (such as development, QA, DWH, artists and sysadmins).

The best way to move away from those anti-patterns is by automating and giving visibility when detecting unhealthy jobs, which might kill the Jenkins ecosystem. During this presentation, we will share our journey of ensuring we apply Jenkins best practices, automation and evangelization. This has led to success in an environment that fosters freedom and collaboration, making continuous integration/automation fast, reliable, maintainable and scalable. You will hear about our problem, what we did to tackle it, what we learned and what we foresee for the future.