-
Type:
Bug
-
Resolution: Not A Defect
-
Priority:
Major
-
Component/s: git-client-plugin
-
Environment:Windows 10
Jenkins 2.87
Git Client Plugin 3.6.4
Git Plugin 2.6.0
Git for Windows 2.15.windows.1 (Credential Manager NOT installed)
Advanced sub-modules behaviors options checked:
"Recursively update submodules"
"Use credentials from default remote of parent repository"
SSH private key stored in Jenkins Credentials
Windows 10 Jenkins 2.87 Git Client Plugin 3.6.4 Git Plugin 2.6.0 Git for Windows 2.15.windows.1 (Credential Manager NOT installed) Advanced sub-modules behaviors options checked: "Recursively update submodules" "Use credentials from default remote of parent repository" SSH private key stored in Jenkins Credentials
See initial Stack Overflow question: https://stackoverflow.com/questions/46518082/jenkins-git-plugin-unable-to-initialize-submodules
I have since updated all components to their latest releases.
The project "Parent_test_repo" includes "Child_test_repo" as a submodule. These are both private repositories. They use the same SSH key, which has been add to the Jenkins credentials.
Building the project results in the parent repository being correctly accessed and clone, but the the "git submodule init" fails with a 128 (access violation?) error.Â
This problem is specific to Windows: On Ubuntu 17.10 it correctly initializes the submodule and the build succeeds.
Variations tried unsuccessfully:
- Using Windows 7 instead of 10
- Using ~/.ssh instead of storing private SSH key in Jenkins
- Using HTTPS login instead of SSH
- Using Bitbucket instead of GitHub
- Using relative paths in submodule URL
I'm concluding it's a Windows-specific issue with submodule authentication.
I am willing to help debug further.
