[HOLD] Multiple concurrent deploys are slow

[roryabraham]

Problem

When a PR is cherry-picked, we wait for staging deploys to finish before commenting in the deploy checklist to alert Applause of the newly-CP'd PR.

However, if we then merge / CP another PR, we run into softprops/turnstyle here. Then the second CP sits around and waits for the pending staging deploy to finish unnecessarily before creating a new version, CPing it to staging, and updating the checklist.

Why this is important

This causes unnecessary delays in the deploy process, particularly in scenarios where we want to complete multiple CP's in a row, which are typically more urgent scenarios. It will be even more important once we have the ability to CP PR's to production, because then production CP's will be delayed waiting for unrelated staging CP's, potentially adding hours to the time it takes for us to get an urgent fix out to users.

Solution

(ideally) Figure out a way to make it so we don't have to wait for staging deploys to finish. Maybe using a post-action hook?

Otherwise, cleverly separate jobs to make all the prep work (i.e: creating a new version, CPing it to staging, etc...) not have to wait.

[roryabraham]

No update.

[roryabraham]

Not a priority

[roryabraham]

Also would like to bundle this together with a suite of deploy improvements

[roryabraham]

No update

[roryabraham]

No update

[roryabraham]

Dropping, see #12021 (comment)

[MelvinBot]

@roryabraham, this Monthly task hasn't been acted upon in 6 weeks; closing.

If you disagree, feel encouraged to reopen it -- but pick your least important issue to close instead.

[melvin-bot]

@roryabraham, this Monthly task hasn't been acted upon in 6 weeks; closing.

If you disagree, feel encouraged to reopen it -- but pick your least important issue to close instead.

[melvin-bot]

@roryabraham, this Monthly task hasn't been acted upon in 6 weeks; closing.

If you disagree, feel encouraged to reopen it -- but pick your least important issue to close instead.