Recent Blog Posts

Jenkins, Docker and DevOps: The Innovation Catalysts -- Part 3

This is the third in a series of blog posts about the ability to greatly accelerate software delivery pipelines - thus, also accelerating innovation - using the combination of Jenkins, Docker and continuous delivery practices.

Next Gen CI/CD: Use Cases, Best Practices and Learning

In this section, we will drill down into key use cases related to Jenkins and Docker, and offer best practices for them.

Setting Up Jenkins EC2 Slaves

I will assume that you have a Jenkins instance up and running and that you know how to setup on-premise slaves. Unless you are running the entire infrastructure on AWS, those slaves should be used to guarantee the minimum availability. As a rule of thumb, the number of on-premise slaves should be calculated in a way that (close to a) hundred percent utilization is accomplished at all times. Anything higher than that should be set up on AWS. We’ll configure them so that new slaves are created when needed, and unused ones are destroyed after a short period of inactivity. In this setting, you’ll be able to meet any demand, thus accomplishing high availability and, at the same time, you’ll pay only when slaves are used. In other words, we’ll combine the best of both worlds (on-premise with AWS). Bear in mind that I refer to high availability only in the context of Jenkins slaves. High availability of Jenkins masters is a different problem that can be solved through the High Availability Plugin included in the CloudBees Jenkins Platform.

Announcing the New CloudBees Partner Center

2015 was an amazing year for the continued growth and success of CloudBees. This is due in large part to the relationships established and fostered with our partners over the past year. To continue the momentum with our partners and to support our ever-growing partner community, we are excited to announce the launch of our new partner portal, CloudBees Partner Center.

Jenkins, Docker and DevOps: The Innovation Catalysts -- Part 2

This is the second in a series of blog posts about the ability to greatly accelerate software delivery pipelines - thus, also accelerating innovation - using the combination of Jenkins, Docker and continuous delivery practices.

Webinar Recording: Continuous Delivery with Jenkins Workflow and Docker Explained

On January 20th, 2016 CloudBees and presented a webinar about Continuous Delivery with Jenkins Workflow and Docker. CloudBees presenter Neil Hudson de-mystified how to create end to end Continuous Delivery pipelines for Dockerized applications. He discussed how Docker solves some of the common challenges that result in the symptom of “Well it worked in the test environment” by showing how Docker allows both the application, its config and the run-time environment to be packaged up as a single artifact and managed through the Software Development Lifecycle.

Scaling Jenkins Slaves

Everyone wants to have a scalable system because it allows us to be able to meet the demands business sets in front of us. The problem, for many of us, is not whether we want to scale (most of us do), but how we scale. In many cases, scaling is a question of adding *more servers* and *configuring* them to be part of our cluster. Even though that sentence sounds correct, it exposes a couple of problems. More servers are often not needed, and, when they are needed, configuring them is a costly operation (each hour people spend working on something is a cost). The result? Business tends to think of the IT department as a liability. It requests more money for more servers, and more people to maintain them. Remember, all successful companies want to scale their business, and, in today's age, IT is the crucial part of that need. The increase in business means increases in demand, the increase in demand means increase in infrastructure. That holds true unless we manage our infrastructure in a better and more efficient way.

CloudBees Releases Amazon ECR Plugin 1.0-Beta

Amazon Web Services (AWS) recently announced the availability of the EC2 Container Registry (ECR). Amazon ECR is a fully-hosted private Docker registry that makes it easy to store your Docker images and use them from the Amazon EC2 Container Service (ECS) to run your containerized application on a scalable infrastructure.

Having trouble subscribing in Chrome?