It’s been far too long since we posted an update on Jenkins Essentials. While it’s not quite ready for users to start trying it out, we continue hacking away on all manner of changes to support the safe and automatic upgrades of a running Jenkins environment. In the meantime, Jenkins contributor Baptiste Mathus took some time to introduce and demonstrate Jenkins Essentials at the recently held EclipseCon France,

Jenkins Essentials

From the talk’s abstract:

The Jenkins Project is working on providing its users with a brand new, strongly opinionated, and continuously delivered distribution of Jenkins: Jenkins Essentials. Constantly self-updating, including auto-rollback, with an aggressive subset of verified plugins.

In this talk, we will detail how this works: how we run and upgrade Jenkins itself. How instances are continuously sending health data back to help automated decision-making about the quality of given new release, and decide to generalize a given version of Jenkins to the whole fleet, or roll it back.

We will end giving an overview of the status of the project: how it’s managed in a fully open manner, from design to code and its infrastructure, and all the radical solutions to imagine and the upcoming challenges for the next months.

I hope you enjoy the video


You can learn more about Jenkins Essentials from GitHub repository, or join us on our Gitter channel.

About the Author
R. Tyler Croy

R. Tyler Croy has been part of the Jenkins project for the past seven years. While avoiding contributing any Java code, Tyler is involved in many of the other aspects of the project which keep it running, such as this website, infrastructure, governance, etc.