Continuous delivery on Heroku

The Heroku platform is designed to maximize developer productivity and provide a great developer experience, from an app’s first build to production and beyond. As part of this focus, Heroku extends the platform with a range of tools that support modern development practices, such as continuous delivery.

Heroku Flow—app-centric, optimized.

Heroku Flow is a structured deployment workflow that combines tight integrations with GitHub, visually presented pipelines, disposable “review apps” and Heroku CI. Heroku Flow is designed to streamline the app release experience by making continuous delivery easy, visual, and efficient.

The components of Heroku Flow include:
Heroku Pipelines

Heroku Pipelines Read docs

Heroku apps that share the same codebase can be organized into deployment pipelines, easily promoted from one stage to the next, and managed through a visual interface.

Heroku CI

Heroku CI Read docs

Heroku CI is a low-setup, visual test runner that integrates with Heroku Pipelines to automatically run your tests on every push to GitHub, using disposable apps with strong dev-prod parity.

Heroku Review Apps

Review Apps Read docs

Developers can spin up a temporary test app for teams to review, discuss, and decide whether to merge changes to their code base during development.

Heroku GitHub Integration

GitHub Integration Read docs

Tight integration between a Heroku app and its GitHub repo enables automatic or manual deployment of merged branches, with notifications in both GitHub and Heroku.

Heroku ChatOps

Heroku ChatOps Read docs

Heroku ChatOps makes team collaboration easier by connecting Heroku Pipelines with Slack. With Heroku ChatOps developers can deploy to staging or promote to production from Slack, or see pull requests, merges, and CI build results within their Slack channel.

Heroku Release Phase

Release Phase Read docs

Release Phase lets you automatically run tasks, such as database migrations, before a release is deployed to production. Release Phase eliminates risky manual deployment steps.