Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Deploying Latest to Heroku with Jenkins CI

DZone's Guide to

Deploying Latest to Heroku with Jenkins CI

· DevOps Zone
Free Resource

Download the blueprint that can take a company of any maturity level all the way up to enterprise-scale continuous delivery using a combination of Automic Release Automation, Automic’s 20+ years of business automation experience, and the proven tools and practices the company is already leveraging.

You can use Jenkins Batch Task Plugin if you want to deploy the latest revision to Heroku. Our deployment has two steps: a rake task that pushes assets to S3/Cloudfront and a git push. So the batch task attached to our repo looks like this.
    git rev-parse HEAD
    echo $GIT_COMMIT
    bundle exec rake heroku:predeploy
    git push git@heroku.com:heroku-app.git $GIT_COMMIT:master

The first two lines are there for logging, so that we know which revision was pushed to Heroku.

We’re now missing two important pieces from Heroku-bartender’s functionality: a visual of which revision has been deployed and the ability to run a task on any previous build.


Source: http://code.dblock.org/deploying-latest-to-heroku-with-jenkins-ci



Download the ‘Practical Blueprint to Continuous Delivery’ to learn how Automic Release Automation can help you begin or continue your company’s digital transformation.

Topics:

Opinions expressed by DZone contributors are their own.

THE DZONE NEWSLETTER

Dev Resources & Solutions Straight to Your Inbox

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.

X

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}