Active
Project:
Site management
Component:
Code
Priority:
Major
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
27 Jun 2014 at 17:54 UTC
Updated:
27 Jun 2014 at 18:03 UTC
Jump to comment: Most recent
When all tickets associated with a particular Git branch are marked as approved, controls appear on the screen for the client to deploy it.
When they choose to deploy, instructions are sent to the deployment system to either (a) deploy to staging, (b) deploy to production, or (c) deploy to staging and production. We'll probably pick one and hardcode it for starters, with the final decision dependent on other tickets.
When a deployment is initiated, the screen updates dynamically with a rough indication of progress and ultimate/success failure, and any other information the client needs to see.
Behind the scenes, the code will run a Git merge, then contact the deployment API to deploy it.
Comments
Comment #1
David_Rothstein commented