Recent Blog Posts

The DevOps 2.0 Toolkit

When agile appeared, it solved (some of) the problems we were facing at that time. It changed the idea that months-long iterations were the way to go. We learned that delivering often provides numerous benefits. It taught us to organize teams around all the skills required to deliver iterations, as opposed to horizontal departments organized around technical expertise (...

Using Jenkins for Disparate Feedback on GitHub

Picking a pear from a basket is straightforward when you can hold it in your hand, feel its weight, perhaps give a gentle squeeze, observe its color and look more closely at any bruises. If the only information we had was a photograph from one angle, we’d have to do...

Backup Jenkins to the Cloud

CloudBees has released a new version of its CloudBees Backup plugin. With this new version, you will be able to backup CloudBees Jenkins Operations Center and CloudBees Jenkins Enterprise instances directly to Amazon S3 and Azure Blob Storage.

Until now, users who...

Want to Win a Free Pass to Jenkins World 2016? Here’s How.

Jenkins World is a must-attend event for insight on DevOps, continuous delivery, and this year it will be bigger and better than ever, featuring top-notch speakers, presentations, training and more. If this sounds like your type of event, then today is your lucky day! From July 13 through August 12, we are providing an...

Preface to The DevOps 2.0 Toolkit

I started my career as a developer. During those early days, all I knew (and thought I should know) was to write code. I believed that a great software designer is a person that is proficient in writing code and that the path to the mastery of the craft was to know everything about a single programming language of choice. Later on, that changed and I started taking an interest...

A new angle to Pipeline-as-Code

Last year we introduced the “Pipeline-as-Code” system, which allows you to define your complete Jenkins Pipeline project—building, testing, staging or deploying, whatever you need—from a Jenkinsfile script right in the same source code repository as your project itself, for compatible SCM systems. With this “marker file” standardized, Jenkins is able to detect...