This repository has been archived by the owner on Sep 9, 2019. It is now read-only.
Automate deployment via Travis #204
Labels
Comments
jmhooper
added a commit
that referenced
this issue
Sep 19, 2016
This commit sets up automated deploys using Travis. The inspiration for many of these changes came from the [Micropurchase app's config](https://github.com/18F/micropurchase/blob/develop/.travis.yml). To enable automated deploys, this commit does the following: - Add a deploy script that takes an environment as an argument and deploys to the appropriate app on cloud.gov - Modify the Travis configuration to add the keys that travis needs to deploy to cloud.gov closes #204
jmhooper
added a commit
that referenced
this issue
Sep 19, 2016
This commit sets up automated deploys using Travis. The inspiration for many of these changes came from the [Micropurchase app's config](https://github.com/18F/micropurchase/blob/develop/.travis.yml). To enable automated deploys, this commit does the following: - Add a deploy script that takes an environment as an argument and deploys to the appropriate app on cloud.gov - Modify the Travis configuration to add the keys that travis needs to deploy to cloud.gov closes #204
Merged
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When the build passes on master, we should deploy to production.
Micropurchase also uses Travis and Cloud.gov so their setup can be used as as guide for how to do this https://github.com/18F/micropurchase/blob/develop/.travis.yml
The text was updated successfully, but these errors were encountered: