This project is DEPRECATED!
The recommended alternative is the Heroku Maven Plugin or the Heroku sbt Plugin (depending on what build tool you are using). The Heroku DevCenter has an article that describes using the sbt plugin with Jenkins, but the approach for the Maven plugin is similar in principle.
A plugin for interacting with Heroku during Jenkins builds.
This plugin is available in the Jenkins plugin manager. To install in Jenkins, go to Manage Jenkins | Manage Plugins | Available | Heroku Plugin for Jenkins | Install. You must restart Jenkins to complete the installation.
The Heroku API key used by build steps can be configured either with a global default or for individual build steps. To configure a global default API key, go to Manage Jenkins | Heroku | Default API Key. This key will be used by Heroku build steps unless otherwise overridden. If no global default is specified, individual build steps must specify their own API keys under their respective Advanced settings. Your Heroku API key can be obtained from your Heroku account page.
All build steps also include the following fields:
The Deploy WAR Artifact build step 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 <packaging>war</packaging>, the mvn package command will output the WAR file into its target directory.
Otherwise, create the WAR file in whatever way is approiate for your build.
After the WAR file is created, add the Heroku: Deploy WAR Artifact build step to your under the Jenkins build configuration
and specify the relative path to the WAR file created in a previous build step to deploy.
The Set Configuration build step adds or updates config vars to the specified app.
The Scale Process build step scales a process type to a specified quantity.
The Run Process build step runs a one-off process on a dyno.
The Rollback build step rolls back to the previous release.
The Restart build step restart the specified app.
The Maintenance Mode build step toggle maintenance mode for a given app.
Follow instructions on setting up your environment from Jenkins
This plugin has a dependency on direct-to-heroku-client, which is not yet in Maven central. To build this plugin, you must first build the client from source:
git clone git://github.com/heroku/direct-to-heroku-client-java.git
mvn clean install -DskipTests
Build the plugin:
git clone git://github.com/heroku/heroku-jenkins-plugin.git
mvn clean package -DskipTests
or with tests:
mvn clean package -Dheroku.apiKey="<test user api key>" -Dheroku.appName="<test app>"
This will create a *.hpi file in the target directory.
On your Jenkins instance, go to Manage Jenkins | Manage Plugins | Advanced | Upload Plugin.
Choose the generated *.hpi file and click upload.
Restart Jenkins.