IssueTracker

Problem you have encountered:

Since earlier today our cloudbuild has started trying to clone submodules (and failing). We don't actually require the submodule to be available during our build, so this new failure is blocking our release pipeline.

What you expected to happen:

Based on https://issuetracker.google.com/issues/123060361 not being closed as completed, I expected it not to try cloning my submodule.

Steps to reproduce:

• Have a submodule in your repo
• Trigger cloudbuild
• Observe that the build fails during the FETCHSOURCE phase when trying to clone the submodule.

Other information (workarounds you have tried, documentation consulted, etc):

It turns out if we change our .gitmodules file to specify the submodule url using https:// instead of git@ then the build works properly and does not attempt to clone the submodule.

Here's the sanitized log for a failing build (the build id is not sanitized):

starting build "8793bca9-a6ae-4fc5-8ef8-c27b7f4fcddf"

FETCHSOURCE
Initialized empty Git repository in /workspace/.git/
From https://github.com/someorg/somerepo
 * branch            abcdefaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa -> FETCH_HEAD
HEAD is now at abcdefa My cool commit message
Submodule 'my/submodule' (git@github.com:someorg/submodule.git) registered for path 'my/submodule'
Cloning into '/workspace/my/submodule'...
Host key verification failed.
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
fatal: clone of 'git@github.com:someorg/submodule.git' into submodule path '/workspace/my/submodule' failed
Failed to clone 'my/submodule'. Retry scheduled