Deploying from Travis CI
Deploying via Git is a quick way to get up and running and is useful for developers. It's not a robust way of pushing out changes though. If we are practicing Continuous Delivery then we may want to deploy on every commit, at least to a UAT environment. But we still want our CI server to act as a gatekeeper and ensure that we only deploy good builds.
Travis CI supports deployment to a wide range of hosting providers (as well as arbitrary deployment via custom scripts). We can tell Travis CI to deploy to Heroku by adding a deploy section to our travis.yml as follows (replacing application-name-12345 with the name of our previously created Heroku application):
services: - mongodb - redis-server deploy: provider: heroku app: application-name-12345 api_key: env: global: - MONGODB_URL=mongodb://localhost/hangman - REDIS_URL=redis://127.0.0.1:6379/
Travis CI will only deploy our application if the build passes. In order for Travis CI to communicate with...
