Set up continuous deployment for different branches/spaces

18F / open-data-maker

make it easy to turn a lot of potentially large csv files into easily accessible open data

Other

199 stars 135 forks source link

Set up continuous deployment for different branches/spaces #247

Open yozlet opened 8 years ago

yozlet commented 8 years ago

Committing to dev, staging and master should push to the dev, staging and production CF spaces respectively. This requires setting our CI service up to do those deployments.

This issue mirrors https://github.com/18F/college-choice/issues/256

yozlet commented 8 years ago

At present, Travis is set up to auto-deploy only to dev, but thanks to the manifest.yml it pushes the app with the name ccapi-staging. Both the space and the app name should depend on which branch is being pushed.