Recent Blog Posts

Jenkins World Speaker Highlight: Secure Container Development Pipelines with Jenkins

This is a guest post by Jenkins World speaker Anthony Bettini, Founder and CEO at FlawCheck.

At FlawCheck, we’re really excited about...

Top 9 Reasons You Need to Go ALL IN and Attend Jenkins World

The countdown is on. Jenkins World 2016 is coming to the Santa Clara Convention Center, September 13...

Service Discovery (The DevOps 2.0 Toolkit)

Service discovery is the answer to the problem of trying to configuration our services when they are deployed to clusters. In particular, the problem is caused by a high level of dynamism and elasticity. Services are not, anymore, deployed to a particular server but somewhere within a cluster. We are not specifying the destination but the requirement. Deploy anywhere as long as...

Jenkins World Speaker Highlight: Continuously Delivering Continuous Delivery Pipelines

This is a guest post by Jenkins World speaker Neil Hunt, senior DevOps architect at Aquilent.

In smaller companies with a handful of apps...

Join the Jenkins World Sticker Competition!

We’re thrilled to announce our first Jenkins Butler design contest! Design a unique version of the Jenkins Butler and submit it before September 9, 2016. Voting will take place at Jenkins World, at the sticker exchange booth hosted by Sticker Mule.

We partnered with Sticker Mule, so the winner who produces the winning design will get a $100 credit on...

Cluster Orchestration (The DevOps 2.0 Toolkit)

When I was an apprentice, I was taught to treat servers as pets. I would treat them with care. I would make sure that they are healthy and well fed. If one of them gets sick, finding the cure was of utmost priority. I even gave them names. One was Garfield, and the other was Gandalf. Most companies I worked for had a theme for naming their servers. Mythical creatures, comic book...

Containers and Immutable Deployments (The DevOps 2.0 Toolkit)

Even though CM alleviated some of the infrastructure problems, it did not make them go away. The problem is still there, only in a smaller measure. Even though it is now defined as code and automated, infrastructure hell continues to haunt us. Too many often conflicting dependencies quickly become a nightmare to manage. As a result, we tend to define standards. You can use only...