在travis-ci成功构建之后,有什么方法可以部署heroku rails应用程序吗?
Travis CI现在已经内置支持部署到Heroku: http : //about.travis-ci.org/blog/2013-07-09-introducing-continuous-deployment-to-heroku/
I just implemented this case with an application of mine. It's actually not that hard to do, but it requires some steps:
.travis.yml
and get the travis_deployer.rb
script travis encrypt your_username/your_repo HEROKU_API_KEY=<your key here>
.travis.yml
in the env -> global section The travis_deployer.rb
file takes care of the ssh keys and the remote branch for heroku.
If you've performed all these steps you .travis.yml
might look like this:
env:
global:
- secure: "1u21hjnmHjkghduUIJhhs76saljlkajdlfhGhgdJgfaVtgasfLLmNBnb87dad="
after_success:
- gem install heroku
- yes | ruby travis_deployer.rb
- heroku keys:clear
- yes | heroku keys:add
- git push heroku master
Here is a version I found on Mark Bates' blog . It's similar to Odi's, just that it relies on the after_script
in your .travis.yml
file alone.
First of all, use Travis' feature to encrypt environment variables so your secret API keys remain protected:
gem install travis travis encrypt username/repository HEROKU_API_KEY=YOUR_HEROKU_API_KEY
Then append the following to your .travis.yml
file:
env: global: - secure: YOUR_SECURED_HEROKU_API_KEY after_script: # Install the Heroku gem (or the Heroku toolbelt) - gem install heroku # Add your Heroku git repo: - git remote add heroku git@heroku.com:YOUR_HEROKU_APP.git # Turn off warnings about SSH keys: - echo "Host heroku.com" >> ~/.ssh/config - echo " StrictHostKeyChecking no" >> ~/.ssh/config - echo " CheckHostIP no" >> ~/.ssh/config - echo " UserKnownHostsFile=/dev/null" >> ~/.ssh/config # Clear your current Heroku SSH keys: - heroku keys:clear # Add a new SSH key to Heroku - yes | heroku keys:add # Push to Heroku! - yes | git push heroku master
And you're done: commit your new changes and enjoy deploying to Heroku via TravisCI.
Edit: If you get any errors on travis encrypt
, this might be your solution .
I had just been thinking of this kind of scenario, though I didn't specifically consider Heroku as the platform of choise. Anyhow, this is what I have come-up with:
I'm sure you could implement a Heroku app that will handle the role of being the deployer host or something even more crazy.
Also, you may wish to try having Travis to notify you via IRC and have another IRC bot on your client side which will have access to you personal SSH key and make a push to Heroku, you could also implement a confirmation interface there by means of having a private conversation with your own bot or scripted GUI interface with a "Go ahead!" button. If you are not so old-school, you can use Hubot for that purpose.
By the way, you could also introduce some sort of staging branch or whatever you like in between some of the above steps. You probably should also use tags and the rollback would just pushing a know working tag into "release/production" from where it'll be picked up by your deployer script.
The technical post webpages of this site follow the CC BY-SA 4.0 protocol. If you need to reprint, please indicate the site URL or the original address.Any question please contact:yoyou2525@163.com.