So I went to a great session at AWS re:invent on using github actions for deploying to AWS. While I’ve already moved a ton of our workflows to actions, deploys is the final piece so it was a very relevant talk/demo (and great presenters)
One question I had was if you set up a workflow on a push to master which triggers a deploy, do other pushes queue up behind this (because clearly 2 deploys running at the same time would result in . The presenters didn’t know so I just tested it…and…they don’t .
Merging a PR to master triggers a deploy and then a merge of a seperate PR to master while the other action is running causes 2 actions running at the same time which gives me a bad day.
Is anyone else solving this currently? I’m thinking of some kind of lock when a deploy is running but it will mean a ton of minutes are used for the ‘waiting’ deploy while it’s trying to get the lock. Some of our deploys run for quite a long time and we regularly have multiple PRs in “merge flight” so it’s a real problem.
Anyway, interested to see if anyone else is doing this and/or solved it. Or if there’s something on the GH actions near term roadmap?
ps: and if the chaps who presented at DOP322 frequent this board, thanks again for the great talk!