Skip to content
This repository has been archived by the owner on Nov 7, 2018. It is now read-only.

Set up continuous deployment for different branches/spaces #247

Open
yozlet opened this issue Dec 14, 2015 · 1 comment
Open

Set up continuous deployment for different branches/spaces #247

yozlet opened this issue Dec 14, 2015 · 1 comment
Assignees
@sharms

Comments

@yozlet
Copy link
Contributor

yozlet commented Dec 14, 2015

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 RTICWDT/college-scorecard#256
@yozlet yozlet self-assigned this Dec 14, 2015
@ultrasaurus ultrasaurus mentioned this issue Dec 14, 2015
Open
@yozlet
Copy link
Contributor Author

yozlet commented Dec 14, 2015

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.

@yozlet yozlet assigned sharms and unassigned yozlet Feb 25, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@sharms sharms

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@sharms @yozlet