One of my concerns is separating the task of deploying and developing. This breaks down into a couple things:
- Making new builds available
- Deploying new builds.
I'd like our deploy process to look like this:
- Update source control (either tag a new release, or push new code, whatever)
- Deploy team is notified of new build available (or polls for new builds)
- This is unimportant, but Github webhook, or cron job on deploy servers are both trivial to implement)
- Deploy team opens up web UI, sees available builds and clicks a button for the build they want to deploy (for whatever target, e.g. staging, prod, etc).
I can see this web UI as an addon/plugin based on @lukemelia's talk at EmberConf2015, but wanted to get thoughts on the use case.
One of my concerns is separating the task of deploying and developing. This breaks down into a couple things:
I'd like our deploy process to look like this:
I can see this web UI as an addon/plugin based on @lukemelia's talk at EmberConf2015, but wanted to get thoughts on the use case.