Recent Blog Posts

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 this feature for AWS. We use an AWS CloudFormation template to provision a working version of Jenkins Essentials, automatically configured to: dynamically provision EC2 agents, using the EC2 plugin; use the Artifact Manager on S3 plugin, so that artifacts are not stored anymore on the controller’s file system, but directly in an S3 bucket. I recorded a short demo video last week showing the basics of this: While there are still many items to complete to provide a usable version for end-users, we are making steady progress towards it. You can learn more about Jenkins Essentials from the GitHub repository, or join us on our Gitter channel.

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 Jenkins Essentials at the recently held EclipseCon France, 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.