We’re on the verge of something here, people. A growing number of companies are shipping software in minutes. Yeah, you read that right. Minutes. Not hours, not weeks, months, or longer. Minutes. Often, teams struggle to ship software into the customer’s hands due to lack of consistency and excessive manual labor. Continuous integration (CI) and continuous delivery (CD) deliver software to a production environment with speed, safety, and reliability.

Find out how Cloudsmith + Helm combine to provide you with world-class support for the Kubernetes (k8s) ecosystem. Get your own private Helm repository today.

How to monitor thousand of endpoints every minute.

Why creating another monitoring service when there are new monitoring services every day?

Automating your deployment process is a critical step towards adopting continuous delivery. For teams that use Bitbucket for hosting their source code, Bitbucket Pipelines provide an easy way to automatically build and deploy when changes are made in your origin repository. The Rollbar team is excited to participate in the launch of Bitbucket Pipes, which make it even easier to configure your pipeline.

In a previous post, we explained the concept of configuration management and presented three of the most popular tools: Chef, Puppet, and Ansible. We also briefly explored the impact that containerization is having on configuration management, and how the two can be used in combination. This article takes a more in-depth look at this relationship by presenting different techniques for using Chef, Puppet, and Ansible to deploy and manage a Kubernetes cluster.

Continuous Integration and Continuous Delivery (CI/CD) is becoming a standard process in organizations that embrace agile development. CI/CD tools like Bitbucket, Bamboo and Jenkins can help by automating many of the build and deployment steps. However, there are still situations where human intervention is required and Opsgenie can make sure the right responders are notified to take quick action.