Queueing builds / concurrent = 1
We've had issues with development code going live, simply by doing:
git push origin master
git push origin live
To try and alleviate the problem, we set concurrent = 1
in config.toml
, but not even that guarantees correct order since a stage is started when another stage is finished as opposed to when all stages for the current job are done.
This is the order of stages ran after running those two pushes from above:
1. build_frontend (live)
2. build_frontend (master)
3. deploy_frontend (live)
4. deploy_frontend (master)
When I expected it to be:
1. build_frontend (live)
2. deploy_frontend (live)
3. build_frontend (master)
4. deploy_frontend (master)
I guess these issues stem from the fact that our stuff is built in a directory mounted from the host, but we need this to access artifacts after a build happens.
Is this the intended behaviour of concurrent = 1
?
Edited by 🤖 GitLab Bot 🤖