Each time we deploy our code to Heroku, a new slug is created; this slug contains all of our application code and assets. Using Heroku's Pipeline, we can promote this slug to another environment without having to go through the slug-compilation process again. This ensures that the slug that we tested and verified in our staging environment is identical to what we push to our production environment. With the Pipeline, we can compare the commits between our applications so that we know exactly what changes we are deploying. It's amazingly useful; here, we will learn how to set it up and use it.
To get started, let's open up a terminal and navigate to our Heroku project by performing the following steps:
First, we need to install the Heroku Pipeline CLI plugin:
$ heroku plugins:install [email protected]:heroku/heroku-pipeline.git Installing heroku-pipeline... done
Note
Heroku Pipeline's GitHub repository at https://github.com/heroku/heroku-pipeline...