We need some kind of lock mechanism, so that phab does not run concurrently and does accidently two deployments for the same installation at once, as this might introduce errors most likely when running in a CI context
I do not see any way to implement this efficiently and will close this for now. Gitlab CI has mechanisms to serialize deployments and we should rely on them.
We need some kind of lock mechanism, so that phab does not run concurrently and does accidently two deployments for the same installation at once, as this might introduce errors most likely when running in a CI context