diggerhq
Run plans or applies in parallel for different projects
Interesting one!! Indeed this would be a game changer. It seems that digger would need to spawn multiple actions in order to acheive this
And the user will need to specify which modules depend on which so that in this case they will wait for the other modules to run
Ideally this has to be done natively in the underlying CI system as well
Hi @frank-bee I think this is how it works already, you can take a look at example here https://github.com/diggerhq/digger_demo_multienv
Bumping up this issue a bit since I believe with multiple recent features like generate_projects, this should be a deal breaker for big projects to not be able to parallel execute multiple runs
hey @luong-komorebi ! If you use digger in backendless mode the runs will be serial, if you use digger with the app on cloud.digger.dev and link it that way the runs will be triggered in parallel (separate jobs)
awesome. Thanks @motatoes , this hasnt changed since we last talked. I suggest closing this issue and document this behaviour. That should be better for users 👍🏻
Document found here https://docs.digger.dev/howto/backendless-mode#:~:text=No%20concurrency%3B%20all%20plans%20/%20applies%20need%20to%20run%20sequentially%2C%20which%20is%20slow
This issue shall be closed ;)