Heroku DevOps: Introduction and Requirements

Updated 3 months ago by Copado Solutions


As part of Multi-Cloud, Copado has developed a series of plugins for different tools that enable you to implement a DevOps process when working with other clouds.

In this article, you will find detailed information about the Heroku plugin and a step-by-step process to set up your Heroku pipeline and start leveraging Copado.

Heroku is a multi-cloud app platform that allows you to build applications in open-source languages such as PHP, Ruby or Java. For more information about Heroku, dive into Salesforce’s  Develop Apps with Heroku trail.

To start leveraging the Copado Heroku plugin, you need:

  • The Copado User and Copado Functions permission sets.
  • An Admin license (you need this license to build the pipeline and also to deploy to production. To deploy to other environments, the User license is enough).
  • A Heroku account.
  • The Copado CLI and the Heroku CLI (the Heroku CLI is only required for developers).


As mentioned in the Introduction, you need access to the Copado CLI, which you will use to commit changes to a user story, and the Heroku CLI, which you can use to build your Heroku app. You also need to install the Heroku plugin (contact your customer success manager to do that) and create a fresh Git repository and some Copado records such as a pipeline and the Environment records for the environments that are part of your DevOps process. 

Follow these instructions to complete the setup process:

  1. First, install the Heroku CLI. For more details on the Heroku CLI and the installation steps, visit Heroku Dev Center.
  2. Next, create a Git repository if you don’t have one to store your Heroku app code.
  3. Then, log in to your Heroku account and create your application and your environments if you haven’t done it yet. 
Considerations when building a Heroku app
When you create an app, you create an instance of the app. Each app has a different instance and a different URL (the url your customers will see will be that of the production instance). Therefore, if you consider this basic Heroku pipeline, Dev ⇨ Staging ⇨  Production, you need to create three different apps, one for the dev stage, one for the staging stage and one for the production stage.
App names are unique. Therefore, each app should have a different name, e.g., heroku-app-dev, heroku-app-staging, etc.

You can find more information about Heroku apps and the step-by-step process to create an app in Heroku Dev Center.

  1. Next, install the Heroku plugin and create the Copado records. You can find the step-by-step process in the article Heroku Plugin Configuration Steps.
  2. Finally, install the Copado CLI. For more information about this tool and how to install it, visit the Copado CLI section on our documentation site.

Once you complete the setup, go ahead and start committing and deploying your changes. For more information about how these processes work, review the article Commit & Deployment Processes in Multi-Cloud.

How did we do?