Release a backend and a frontend in order
When the frontend needs the new backend, merging both at once is a gamble. A grouped release merges them in order and waits for each deploy. Ordered releases are on Pro.
Build the release
- Open Schedule and pick the first pull request (the backend).
- Press Add a step and pick the next one, in the same or another repository. You can have 2 to 10 steps.
- Choose when step 1 starts. Each later step is timed from the one before.
How the next step starts
- After the previous step deploys: waits for a green deploy, the safest option. You can add a pause of up to 240 minutes after the deploy before the next step starts.
- A few minutes after the previous step merges: for deploys you do not want to wait for.
- Timed so both finish about together: for changes that must go live at the same moment.
If a step fails
- The failed step is reverted by auto-revert, and later steps never merge.
- Choose whether a failed step also reverts the earlier steps, or only itself. A step that is skipped (for example you merged it by hand) is not a failure: earlier steps are never reverted for it, and the steps that have not started are cancelled.
- Or carry on: for separate changes, a failed step is reverted and the next one still starts. See the guide on queuing several pull requests.
Background reading: How to release a backend before the frontend (and roll both back) · How to release stacked pull requests safely
More guides: Schedule your first merge · Set up automatic revert for a failed deploy