When I first wrote about Jenkins Evergreen, which was then referred to as "Jenkins Essentials", I mentioned a number of future developments which in the subsequent months have become reality. At this year’s DevOps World - Jenkins World in San Francisco, I will be sharing more details on the philosophy behind Jenkins Evergreen, show off how far we have come, and discuss where we’re going with this radical distribution of...

Evergreen is a distribution of Jenkins we are working on that provides an easy to use and automatically upgrading experience. This year at the conference, there will be not just one, but two talks to present Evergreen to the Jenkins community: Continuously Delivering an Easy-to-Use Jenkins with Jenkins Evergreen, by R. Tyler Croy. Safely Upgrading Jenkins Every Single Day, by Baptiste Mathus. Tyler will present the overall Jenkins...

Jenkins Essentials has been renamed to Jenkins Evergreen since this was written. Jenkins Essentials is about providing a distribution of Jenkins in less than five minutes and five clicks. One of the main ideas to make this a reality is that Jenkins will be autoconfigured with sane defaults for the environment it is running in. We are happy to report we recently merged the change that provides...

Jenkins Essentials has been renamed to Jenkins Evergreen since this was written. 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...

A couple of weeks ago, Tyler mentioned some developer improvements in Essentials that had been recently introduced: the ability for ci.jenkins.io builds to get deployed automatically to an “Incrementals” Maven repository, as described in JEP-305. For a plugin maintainer, you just need to turn on this support and you are ready to both deploy individual Git commits from your repository without the need to run heavyweight traditional Maven releases, and to depend directly on similar commits...

Jenkins Essentials has been renamed to Jenkins Evergreen since this was written. A couple weeks ago, I wrote about the Jenkins Essentials effort, on which we’ve been making steady progress. Personally, the most exciting challenge of this project is defining the machinery to drive automatic updates of Jenkins Essentials, which viewed from a high level, are classic continuous delivery challenges. In this post, I wanted to dive into a bit of the...

Jenkins Essentials has been renamed to Jenkins Evergreen since this was written. In his presentation at the 2017 Jenkins World Contributor Summit, Kohsuke challenged us to continue the work started with Jenkins 2 of making Jenkins easier to install and easier to use. "A user should be successful with Jenkins in under five minutes and five clicks." At that same Contributor Summit, a few of us discussed the idea of...

Lately, perhaps subtle but exciting changes are starting to happen in the Jenkins project. The past few weeks have seen the birth of two new initiatives in Jenkins: Jenkins Essentials and Jenkins X. Each is exciting in its own right, and I encourage interested parties to take a look at their goals and missions and participate in them. But in this post, I want to discuss why together...