Hey all, QQ on stack merging. I'm sure ( as I can ...
# how-do-if
Fynn
02/09/2023, 10:24 AMHey all, QQ on stack merging. I'm sure ( as I can be ) there used to be an option to await the last merge ci to complete before merging the next. Am I imagining this? Is it an option I can't find, or an option I'm craving?
What I'm seeing recently; partly due to our CI being a bit random in run time, is say a stack of three, they merge to master in the right sequence, then ci runs on each merge ( our problem ) which triggers a staging container build & deploy, only lets say branch 2 runs slow, so we deploy b1, b3, b2, result b2 is now deployed. My work around atm is to merge the first n(b1 & b2), set a 5 min timer then do the last one. Thanks.
j
Jacob Gold
02/09/2023, 3:41 PMIf you don't check the
Ignore optional CI status checks➕ 1
f
Fynn
02/10/2023, 10:19 AMNo I've not been using that. I did early on, on larger stacks where I'd of been most of the day waiting.
Fynn
02/10/2023, 10:46 AMJust looked at the merge times on the last 2 stack, 5 seconds between them.
Wondering if its our GH <> GCP CI ... will test on a pure GH CI repo and report back.
s
Sebastien La Duca
02/24/2023, 3:09 PMDid you end up resolving the issue? We've been running into something similar
f
Fynn
02/26/2023, 2:20 PMNo I just ran a stack of 6 for a hobby prj on GH... they all began merging seconds apart.
Fynn
02/26/2023, 2:25 PMI'm still working around it by leaving one in the stack to push it over to the right release.
Fynn
02/26/2023, 2:28 PMThis being the outcome, I have cancel ci if new push configured. So in this proj, it's not a problem as such. Hope this helps in someway.
JobID:
Mz2xeN5op0ke8BS8zhdI