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

Jenkins keeps printing "Enter the passphrase for key: 'ssh<hash>key': " for every build

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Minor
    • Resolution: Fixed
    • Component/s: git-plugin
    • Labels:
      None
    • Environment:
      linux
    • Similar Issues:

      Description

      The message seems to be printed to the stderr every time the new build is started. It keeps polluting the shell as it gets printed over the command line, or on top of vi.

      The jenkins user has all the credentials configured and it all works, but there is no passphrase used for the key to access git repos via SSH

        Attachments

          Issue Links

            Activity

            Hide
            markewaite Mark Waite added a comment -

            Please provide more detail about the configuration where you're seeing the unexpected message.

            For example:

            • command line git version?
            • git plugin version?
            • git client plugin version?
            • URL used to access the git repository?
            • are you certain that no passphrase is used for the private key registered in the Jenkins credentials?
            • job configuration which shows the issue?
            • master or a slave which is showing the message?
            • are there any configurations which use the same URL scheme yet do not display that message?
            • describe further what you mean by "it all works"?
            Show
            markewaite Mark Waite added a comment - Please provide more detail about the configuration where you're seeing the unexpected message. For example: command line git version? git plugin version? git client plugin version? URL used to access the git repository? are you certain that no passphrase is used for the private key registered in the Jenkins credentials? job configuration which shows the issue? master or a slave which is showing the message? are there any configurations which use the same URL scheme yet do not display that message? describe further what you mean by "it all works"?
            Hide
            eguess74 eguess74 added a comment -

            Jenkins 1.578
            git 2.1.2
            git plugin 2.2.5
            git client 1.10.1
            credentials 1.9.4
            gerrit plugin 2.2.1

            user has .ssh folder with the SSH key configured to access gerrit
            no passphrase is used to generate the key, master is printing this error message;
            Gerrit is the SSH manager, the url for the repos is of the same format for all projects "server:/project"
            As there is no other info but just this cryptic error i can't say which builds are triggering this, but seems like not all of them or not everytime.
            "All works" means that there is no problems accessing Gerrit server and getting info from it or send info to it - i.e. configuration is correct, builds are going fine.

            Hope that helps

            Show
            eguess74 eguess74 added a comment - Jenkins 1.578 git 2.1.2 git plugin 2.2.5 git client 1.10.1 credentials 1.9.4 gerrit plugin 2.2.1 user has .ssh folder with the SSH key configured to access gerrit no passphrase is used to generate the key, master is printing this error message; Gerrit is the SSH manager, the url for the repos is of the same format for all projects "server:/project" As there is no other info but just this cryptic error i can't say which builds are triggering this, but seems like not all of them or not everytime. "All works" means that there is no problems accessing Gerrit server and getting info from it or send info to it - i.e. configuration is correct, builds are going fine. Hope that helps
            Hide
            markewaite Mark Waite added a comment -

            Will be fixed with release of git client plugin 2.6.0 (so long as the command line git in use on the agent is git 2.3.0 or newer. No fix for older versions of command line git.

            Show
            markewaite Mark Waite added a comment - Will be fixed with release of git client plugin 2.6.0 (so long as the command line git in use on the agent is git 2.3.0 or newer. No fix for older versions of command line git.
            Hide
            markewaite Mark Waite added a comment -

            Included in git client plugin 2.6.0, released 27 Oct 2017

            Show
            markewaite Mark Waite added a comment - Included in git client plugin 2.6.0, released 27 Oct 2017

              People

              • Assignee:
                Unassigned
                Reporter:
                eguess74 eguess74
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: