-
Notifications
You must be signed in to change notification settings - Fork 145
Using Release Status for Chained Continuous Deployment
Scott Ringwelski edited this page Feb 21, 2019
·
1 revision
Note: This is an unreleased and unofficial feature. This feature lets you add statuses to commits, and based on those commits chain other stacks together. An example use case would be to require a successful staging deploy, wait 3 minutes, and then deploy production.
In your staging yml, add:
status:
context: shipit/staging
delay: 3m
this will tell shipit to track a status with the key "shipit/staging" on the commit. It will mark it as success / fail based on the staging deploy. The 3 minute delay means it will wait 3 minutes after successful deploy to mark the commit status as successful.
Then, in production yml, add:
ci:
require:
- shipit/staging
which tells the production stack that a successful staging deploy is required for a production deploy.