Closed maxenced closed 5 years ago
So, checked the code, it seems the behavior is not directly related to the retrygitcommands option.
As I understand it, issue is that https://github.com/xorpaul/g10k/blob/d9d50df1ad60c6da91b15d48a75c308363e453c5/git.go#L81 does not check return value from doMirrorOrUpdate
So we have no way to detect that environment has deployed correctly (unless we grep in logs)
Please check if v0.6.1 works for you: https://github.com/xorpaul/g10k/releases/tag/v0.6.1
We have a big environment with 380 modules. When deploying a new environment with
-maxworker 2 -maxextractworker 2 -retrygitcommands
on 2 nodes I don't get consistent, neither satisfying results :When digging, it seems that when we use
-retrygitcommands
g10k will retry once, and then ignore silently if the second try fails too :But at the end the run does not raise any error :
but some modules are missing