Getting Started with the Heroku Plugin for Atlassian Bamboo
Last updated 16 June 2015
This article only applies to applications in Heroku Enterprise for Java packages.
You can integrate Atlassian Bamboo with Heroku using the Heroku Plugin for Bamboo. This article will guide you through setting up the plugin and deploying WAR artifacts to your Heroku apps from Bamboo to build continuous integration workflows.
- Atlassian Bamboo 4.0 or higher and a working knowledge of the application.
- A Heroku account. Sign up for an account, if you don’t have one.
- In Bamboo, go to Administration | Plugin Manager | Install Plugins.
- Search for the Heroku Plugin for Bamboo.
- Expand the entry and click Install.
Example WAR Deployment Plan
- In Bamboo, click on Create Plan | Create a New Plan.
- Complete the form with details about your project and click Configure Tasks.
- Add a task to create the WAR artifact to your plan. For example, in Maven-based projects, this would typically be the
- Click Add Task and choose the Heroku: Deploy WAR Artifact task.
- In the configuration form, specify the API Key, App Name, and WAR File to use. Your API can be found on the Heroku account page. If the app name specified does not exist, it will be created for you. The WAR file should be the relative path to the artifact created in the previous step. Click Save.
- Complete any other plan details and enable the plan.
- click Run | Run Plan.
This task deploys a WAR file generated by your build directly to a Heroku app.
To deploy a WAR file, first make sure your build is successfully creating a deployable WAR file.
If you are using Maven with
mvn package command will output the WAR file into its
Otherwise, create the WAR file in whatever way is appropriate for your build.
After the WAR file is created, add the Heroku: Deploy WAR Artifact task to your plan configuration and specify:
- API Key: Your Heroku API key to use for deployment. Your Heroku API key can be obtained from your Heroku account page.
- App Name: The app to which to deploy.
- WAR File: Relative path to the WAR file created in a previous build step to deploy