Skip to content

Instantly share code, notes, and snippets.

@kimmobrunfeldt

kimmobrunfeldt/heroku.md

Created November 16, 2015 11:54
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save kimmobrunfeldt/a31faa254af3303d9f6d to your computer and use it in GitHub Desktop.
Save kimmobrunfeldt/a31faa254af3303d9f6d to your computer and use it in GitHub Desktop.
Download ZIP
Heroku pipelines
Raw
heroku.md

Heroku Pipelines, GitHub integration and Review apps

In short, they are awesome. They have some limitations though.

Pipelines

Clear dash board to which documents all the environments and deployment flow.

Heroku forces to categorize your existing applications, e.g. myapp-dev.herokuapp.com to these three slots in the pipeline:

development -> staging -> production
  • myapp-dev.herokuapp.com -> development slot
  • myapp-qa.herokuapp.com -> stating slot
  • myapp-prod.herokuapp.com -> production slot
  • etc.

You can have more than one app per slot, for some more complex setups.

GitHub integration

Deploy e.g. master branch automatically to your development application. You can force that CI must pass before deployment.

Review apps

From each pull request created to GitHub, start a new Heroku app where you can test all the changes.

Review apps are always related to another running app. For example if you setup review apps for dev app, it copies environment variables from that dev app to the newly created review app.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment