DevOps Zone is brought to you in partnership with:

Daniel Doubrovkine (aka dB.) is one of the tallest engineers at Art.sy. He founded and exited a successful Swiss start-up in the 90s, worked for Microsoft Corp. in Redmond, specializing in security and authentication, dabbled in large scale social networking and ran a big team that developed an expensive Enterprise product in NYC. After turning open-source cheerleader a few years ago in the worlds of C++, Java and .NET, he converted himself to Ruby and has been slowly unlearning everything he learned in the last 15 years of software practice. Daniel has posted 46 posts at DZone. You can read more from them at their website. View Full User Profile

Deploying Latest to Heroku with Jenkins CI

12.02.2011
| 4226 views |
  • submit to reddit
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



Published at DZone with permission of its author, Daniel Doubrovkine.

(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)