Introducing Continuous Delivery for Puppet Enterprise 2.2
In June of 2018 we launched Continuous Delivery for Puppet Enterprise 1.0, a solution designed to help Puppet Enterprise customers streamline and simplify the continuous delivery of their Puppet code. As a prescriptive workflow, Continuous Delivery for Puppet Enterprise gives customers an easy way to test and deploy Puppet code across their environments.
Over the last few months we’ve improved the product by adding new features and enhancements, and today we’re excited to announce the release of Continuous Delivery for Puppet Enterprise 2.2. In this release, we’ve focused on deployment approvals, Azure DevOps support and scaling support for impact analysis.
Many Puppet Enterprise customers have several teams that contribute to the Puppet code base. As teams release new Puppet modules, the change proposals need to be reviewed by the central Puppet team to ensure they are safe. This creates a bottleneck, slows down changes moving through the delivery process, and makes it more difficult for teams to contribute to infrastructure management.
With Continuous Delivery for Puppet Enterprise 2.2, we’re introducing a deployment approval workflow to help address this issue. Now, teams that contribute Puppet code can use Continuous Delivery for Puppet Enterprise to deploy changes to pre-production environments to ensure each change is safe, effective, and passes tests. The central Puppet team can select the mission-critical Puppet environments that require review before deployments are allowed. Since the change has already independently been deployed to pre-production environments in the Continuous Delivery for Puppet Enterprise pipeline, the Puppet team can make quick order of reviewing the change and approving it for deployment to production.
Support for Azure DevOps
For customers who keep their Puppet code in Azure DevOps, Continuous Delivery for Puppet Enterprise 2.2 can now monitor changes to a module or control repository and trigger the relevant pipeline to test and deploy the change. This gives Azure DevOps users the advantages that come with simplifying the continuous delivery of their Puppet code.
In October, we introduced impact analysis: a revolutionary feature for Continuous Delivery for Puppet Enterprise. With impact analysis, teams have the availability to review new and proposed Puppet code changes to quickly assess the risk a change will pose to their environments, all before the proposed code change is even merged. Low-risk changes can be quickly approved and deployed, while higher-risk changes can be carefully scrutinized.
With the release of Continuous Delivery for Puppet Enterprise 2.2, we’ve added scaling support for large-scale environments using impact analysis. Users now have the ability to configure how many node catalogs should be compiled in parallel for a given impact analysis report.
We’re excited to share these great new features and the other improvements we’ve made in Continuous Delivery for Puppet Enterprise 2.2. We continue to focus on user enhancements and solving our customers’ problems with intuitive tools for Puppet code that offer better testing and deployment, which in turn help our customers ship changes and additions with speed and confidence.
Carl Caum is an engineering product manager at Puppet.