- 최신
- 최다 투표
- 가장 많은 댓글
So I finally found the reason by creating some test build, so I'm sharing the solution I found below.
Solution
If you are using multiple sources for your build project, get sure that Git Clone Depth is set to 1 for all your sources. <br>
Git clone depth defaults to "Full", so if you have built your project with CloudFormation get sure to include GitCloneDepth: 1 in your template SecondarySources list.
Explanation
Not sure about what has changed internally, but there seems to be some kind of timeout when cloning the repos, even though the error message is unclear about that. <br> As of today (2020-10-20), this error is reproductible if you have multiple repos containing enough commits, by creating an empty test project and including 3 additional sources. The build will fail with the same error message before starting.
Once I was able to reproduce the issue, I've tried fiddling around with clone depth and it finally worked. Again, I'm not sure if this is temporary or will be fixed, but as of yesterday (2020-10-19), this workaround was not necessary.
Edited by: drolland on Oct 20, 2020 5:37 AM
Hi drolland,
Would you PM me build ARNs of affected builds? Preferably one before and one after you noticed this behavior change. I'd like to help investigate this further.
You are a lifesaver mate. It indeed was a git clone depth issue. When I set it to 1, the code build job started working again. In my case, even the logs were not getting printed in the cloudwatch. Thanks a ton!