Safely Upgrading Jenkins Every Single Day

At the last contributor Summit, Kohsuke Kawaguchi challenged us to make Jenkins usable from zero to continuously delivering a project in under five clicks and less than five minutes.

We are working on providing a brand new, strongly opinionated and continuously delivered distribution of Jenkins: Jenkins Evergreen. It is constantly self-updating, including auto-rollback, with an aggressive subset of verified plugins.

In this talk, we will detail how we upgrade Jenkins itself. How instances are sending health data back to the project to help automate decision-making about the quality of new releases, generalize a given version of Jenkins or a plugin to the whole fleet, or roll it back.