Check out Habitat - automation that travels with your app. Learn more.
Dismiss

Chef Delivery

Continuous Delivery Made Fast, Safe and Transparent at Any Scale

Try the Chef Delivery Tutorial

Chef Delivery is a Continuous Delivery workflow engine that allows teams across your entire organization to provision infrastructure, deploy applications, and manage configuration changes. It utilizes a fixed shared-pipeline model: every change must flow through the same phases and gates prior to being released. But the exact set of steps necessary in each of those phases is highly customizable.

Download the White Paper, Learn More about Delivery and Chef: Automation and the Devops Workflow

DevOps is how we do things at Ooyala. We're building out Chef Delivery to be the foundation for our workflow, so our engineering team has a single pipeline to drive our development.

The Benefits of Chef Delivery

Adopt a Common Workflow

Chef Delivery provides an effective and reusable workflow pattern for consistency, speed and safety when managing changes to your applications and infrastructure. This workflow pattern chains together various phases of validation (or pipelines) which are static and whose structure cannot be modified, creating a common basis for managing all change consistently.

Visualize the Flow of Changes

All changes that go through the pipeline are visualized so you can immediately see how an initial idea is developed and goes to production. Dashboards and notifications make the entire process transparent.

Easily Manage Dependencies

When a change is made in Chef Delivery, the change is fully validated on its own and also integration tested with all of its dependent applications. If any dependent application stops working after your proposed change is applied, then all changes to both are temporarily blocked until the integration issue can be resolved. Other non-related changes can still be released.

Greater Governance and Visibility

Chef Delivery's integration with Chef Analytics allows you to see which team members introduced which changes, revision histories, discussions/comments, who approved which change, and where any given change is within the release process. Chef Delivery also includes several access roles so you can easily create separation of duties between users.

How Chef Delivery Works: One Pipeline for All Changes

In Delivery, every cookbook and application has its own repository. You can use Delivery's own internal Git repository, or you can use an external GitHub or Bitbucket repository. When a check-in occurs the change enters the pipeline. The pipeline is made up of six stages: Verify, Build, Acceptance, Union, Rehearsal, and Delivered. Your changes progress from one stage to another by passing a suite of automated tests. The stages and the phases are fixed for all Delivery pipelines, but what happens within any given phase is up to you.

The last three stages of the pipeline are shared. Their purpose is to assess the impact of the change in the context of the entire set of projects that comprise the system as a whole. Consequently, not only must changes pass local tests, but related, downstream components and services that rely on a changed component must pass those tests, as well. Only those changes that pass are promoted, so deployments to production are safe.

Set Up a Delivery Demo

Request Today

Features of Chef Delivery

SCM Integration

Delivery ships with an internal Git repository, and can also be configured to work with your private repos in GitHub and Bitbucket.

Review GitHub SCM Integration Docs Review BitBucket SCM Integration Docs

Notifications

Users can subscribe to email notifications for projects they care about. Delivery also supports notifications via Slack.

Review Email Notifications Docs Review Slack Notifications Docs

Disaster Recovery

Delivery can be installed with a standby server. Data is replicated rom the primary to the standby with a simple failover option to restore service quickly in the event of a failure.

Review Disaster Recovery Docs

SAML Authentication

Delivery can be configured to route authentication requests to an external IdP via SAML.

Coming Soon

Chef Delivery Resources

Delivery Tutorials

Delivery Docs

Delivery CLI

Delivery Truck

Webinar

Chef Delivery: A Guided Tour