Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-47832

Unable to initialize private submodules due to access error (Windows-only)

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Not A Defect
    • Component/s: git-client-plugin
    • Labels:
    • Environment:
    • Similar Issues:

      Description

      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.

        Attachments

          Activity

            People

            Assignee:
            markewaite Mark Waite
            Reporter:
            mplavcan Matthew Plavcan
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: