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

Git plug-in tries to use 'git.cmd' on Unix

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Not A Defect
    • Component/s: git-plugin
    • Labels:
      None
    • Environment:
      Jenkins 1.404, Jenkins Git 1.1.6.
    • Similar Issues:

      Description

      If I don't explicitly configure the Git tool location for a slave, the Git plug-in assumes the command to be 'git.cmd' regardless of the platform.

      Example from job log on Solaris 5.10:
      ERROR: Cause: Error performing command: git.cmd clone -o origin ssh://<repo> <workspace>
      git.cmd: not found

      It should be noted that this behaviour is seen in a matrix project, with both Windows and Unix slaves. It's possible that the "mother" job Jenkins uses to trigger the jobs on the slaves runs on Windows, and that this confuses the Git plug-in somehow.

      Why is Git's tool location parameter called 'Home' btw (that's the parameter I have to set to 'git')?

        Attachments

          Issue Links

            Activity

            aknuds1 Arve Knudsen created issue -
            aknuds1 Arve Knudsen made changes -
            Field Original Value New Value
            Description If I don't explicitly configure the Git tool location for a slave, the Git plug-in assumes the command to be 'git.cmd' regardless of the platform.

            Example from job log on Solaris 5.10:
            ERROR: Cause: Error performing command: git.cmd clone -o origin ssh://&lt;repo> <workspace>
            git.cmd: not found

            Why is Git's tool location parameter called 'Home' btw (that's the parameter I have to set to 'git')?
            If I don't explicitly configure the Git tool location for a slave, the Git plug-in assumes the command to be 'git.cmd' regardless of the platform.

            Example from job log on Solaris 5.10:
            ERROR: Cause: Error performing command: git.cmd clone -o origin ssh://&lt;repo> <workspace>
            git.cmd: not found

            It should be noted that this behaviour is seen in a matrix project, with both Windows and Unix slaves. It's possible that the "mother" job Jenkins uses to trigger the jobs on the slaves runs on Windows, and that this confuses the Git plug-in somehow.

            Why is Git's tool location parameter called 'Home' btw (that's the parameter I have to set to 'git')?
            ohtake_tomohiro OHTAKE Tomohiro made changes -
            Link This issue is duplicated by JENKINS-9199 [ JENKINS-9199 ]
            ohtake_tomohiro OHTAKE Tomohiro made changes -
            Link This issue is duplicated by JENKINS-9200 [ JENKINS-9200 ]
            sogabe sogabe made changes -
            Status Open [ 1 ] Resolved [ 5 ]
            Resolution Not A Defect [ 7 ]
            markewaite Mark Waite made changes -
            Status Resolved [ 5 ] Closed [ 6 ]
            rtyler R. Tyler Croy made changes -
            Workflow JNJira [ 139357 ] JNJira + In-Review [ 204992 ]

              People

              • Assignee:
                abayer Andrew Bayer
                Reporter:
                aknuds1 Arve Knudsen
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: