Humble semi-technical blog of Pat Wangrungarun

Heroku and Travis

27 April 2013 in heroku, travis · view history

The story was this, I would like to have a CI to get my code from GitHub, maybe run some test, and deploy it to Heroku. So I could commit to one place (master) and everything would be set up. Travis is very handy in this, but require some configurations.

Well I’ve covered most of my Travis knowledge on previous post so there’s nothing much here. Let’s see my configuration for the upcoming phatograph2013 then.

- 1.9.3
- if [[ "$TRAVIS_BRANCH" != "master" ]]; then exit 0; fi
- wget -qO- | sh
- git remote add heroku
- echo "Host" >> ~/.ssh/config
- echo "   StrictHostKeyChecking no" >> ~/.ssh/config
- echo "   CheckHostIP no" >> ~/.ssh/config
- echo "   UserKnownHostsFile=/dev/null" >> ~/.ssh/config
- heroku keys:clear
- yes | heroku keys:add
- yes | git push heroku master
  - secure: ! 'FZ4Os+3zidYERHmdesrifZO47XGy7jOfH4v/wbYofbRhLQJUwplQHFVF6aHi

This build came up from many really nice posts. I would like to thank them all here. The trick, is you need to encrypt your Heroku API key.

$ travis encrypt HEROKU_API_KEY=<your_heroku_key> --add

The command would generate a secure: property. Another note at this line:

- if [[ "$TRAVIS_BRANCH" != "master" ]]; then exit 0; fi

I have the CI perform only commits to master, so the feature branch commits won’t trigger the code deployment.

And because I don’t have any test suite for this site. So I have to let the rake run nothing

# !/usr/bin/env rake
# Add your own tasks in files placed in lib/tasks ending in .rake,
# for example lib/tasks/capistrano.rake, and they will automatically be available to Rake.

require File.expand_path('../config/application', __FILE__)


task :default => []