GitHub App VCS Root submodules checkout fails

Symptoms

• VCS Root is configured using the GitHub App connection.
• The repository pointed to by this VCS Root contains submodules.
• The checkout fails with an error similar to: Failed to perform checkout on agent, likely cause: Corrupted filesystem permissions Submodules checkout failed: /usr/bin/git -c core.askpass=/mnt/data/BuildAgent/temp/buildTmp/pass17900592982435065530 -c core.askpass=/mnt/data/BuildAgent/temp/buildTmp/pass11240121244591257663 -c core.askpass=/mnt/data/BuildAgent/temp/buildTmp/pass13433705773041986450 -c credential.helper= -c credential.helper=/mnt/data/BuildAgent/temp/buildTmp/credHelper18152699910408786095.sh fetch --progress --recurse-submodules=no origin +refs/*:refs/* command failed. exit code: 128 stderr: /mnt/data/BuildAgent/temp/buildTmp/credHelper18152699910408786095.sh get: line 1: /mnt/data/BuildAgent/temp/buildTmp/credHelper18152699910408786095.sh: No such file or directory remote: Repository not found. fatal: repository 'https://github.com/<...>/<...>.git/' not found

Cause

When the VCS Root is created using the GitHub App connection, the issued token is scoped to the single repository selected during VCS Root creation. TeamCity can't access the external submodule repository with this token.

Resolution

It is possible to issue a token scoped for multiple repositories:

1. Open the VCS Root settings > Authentication > Token > Edit > Generate a new token.
2. Select the GitHub App connection to use.
3. Specify the repositories when generating a new token.