I had a working project setup in Jenkins. I am running Git on the same server as Jenkins does, so I did setup the project to grab sources from my local git project with Repository URL "/volume1/git_repos/my_cv.git" and execute some build steps. Jenkins was successfully fetching the project, executing npm install and other build steps I configured for the job.

Since I changed the git project to remove some local files from it that are actually another project and brought them back by adding that other project as git submodule with URL "git://github.com/melo0187/jsonresume-theme-paper-ger", my builds fail.
In the console output of the Jenkins project I can see that "git submodule update --init --recursive --remote" is called, but the submodule´s corresponding path in the project workspace is empty. The submodule is never fetched, but there is no error in the console output related to git. Only later, when calling npm install, errors are reported, which is to be expected, because of the missing submodule.

I can do both "git clone --recurse-submodules" or "git clone" followed by "git submodule update --init --recursive" on "ssh://[user]@melo.myds.me/volume1/git_repos/my_cv.git" with success (prodiving user's password of course). The project AND the submodule get fetched, so the project and it's submodule setup itself are working.

Is the mix of main repos on local paths (like "/volume1/git_repos/my_cv.git") and submodules on remote paths (like "git://github.com/melo0187/jsonresume-theme-paper-ger") not supported? It feels strange that no error is reported, although the submodule is not fetched.

Any help is much appreciated and I am of course willing to help and provide as much information as I can.

Thanks in advance for any feedback!