Babylon's CI Setup clones the repo 5 times

Looking at the CI setup on azure for a PR I’m working on here, I can see the repo is cloned 5 times for the same commit. Is their a reason that it isn’t just cloned once and all the checks are run on the same clone?

Edit: Wrong category, sorry

Yup so that the tasks could be parallelized across servers

1 Like

Interesting… Is it possible to run the tasks on one server so that the repo is only cloned once and npm is only installed once, but the tasks are still run in parallel (maybe use 1 server that is 5x more powerful than the current ones, assuming they run on seperate instances?)

1 Like