Is it possible to require deploys in a specific order?

[johnseekins-pathccm]

Details

Let's say we have two environments: environment_targets: Staging,Production. This works fine and deploys work against both environments just fine. But what if we want to ensure that a user deploys to Staging before they're allowed to deploy to Production? Essentially, is there a way to, similar to requiring reviews, require an environment be successful before another environment can be deployed to?

[GrantBirki]

👋 Hey @johnseekins-pathccm, thanks for opening this issue! This is not the first time I have heard this request and I think its something that warrants a deep dive now. I will schedule some time to investigate if this can be done, and if so... implement it. Keep some 👀 on this issue and I'll update it as I go! It might not be right away as my schedule is pretty tight but I'll get to it when I'm able. Thank you! 🙇

[GrantBirki]

@johnseekins-pathccm I was actually able to complete this faster than expected. I have published a pre-release v9.8.0. Would you be able to test this out and let me know how it works? Thanks! 🙇

[johnseekins-pathccm]

Sorry for the bad message. This works just fine. Thanks for the quick turn-around!

[johnseekins-pathccm]

Actually...no. The order enforcing works too well:

[johnseekins-pathccm]

For some additional clarification:
sha matches in both the successful Staging deploy and the failed Production deploy.

[GrantBirki]

@johnseekins-pathccm would you be able to copy/paste your actions config for the branch-deploy step here or re-run your job with debug logs and paste those too? Feel free to redact anything that might be considered sensitive and I'll take a look to see what's up.

[GrantBirki]

One thing that I am noticing is that I don't see one of the little green rockets (🚀) in your screenshot. Usually if a branch successfully deploys it will say so on your pull request just below that "Deployment Results ✅" comment. I don't see that in your case so it would make sense that the deployment to Production would fail because Staging was never fully deployed.

Here is an example of it working for me: