Chain your deployments
Today we're announcing a feature that will give you more power over the way your deployments are triggered. In some cases you may want to trigger a deployment in one environment only after another one has deployed successfully or you may want to trigger deployments for multiple repositories one after another. Well, now you can.
Setting this up is very easy. As soon as you have two environments in your account, no matter if they are in different repositories or not, you can set up deployment triggers for them. On the environments page, here's how the trigger setup looks:
Once the trigger is set up, on every successful deployment to the main environment, the dependent environment will be deployed. This allows for some very interesting deployment pipelines and we can't wait to hear what you do with this feature. Once you set up a trigger, for your convenience you should be able to see the information about it in the environment you're triggering deployment in:
I hope you find this feature useful and please, let us know if you have any concerns, questions or ideas on how we can improve things.