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

SCM workspace checkout for perforce can't access the ssh-agent

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • ssh-agent-plugin
    • None
    • Ubuntu linux, chrome, Jenkins 1.606, perforce-plugin 1.3.34, ssh-agent-plugin 1.5

      Original problem discussed in ticket JENKINS-27655 against perforce-plugin. After discussion and investigation, I found that a similar problem for the git-plugin was fixed in ssh-agent-plugin for JENKINS-12492, so I'm refiling this bug against ssh-agent-plugin.

      Quick summary is that I have my ssh key credential loaded properly into ssh-agent-plugin, and while the key is available to the build steps themselves (such as a shell execution), the key is NOT available to the SCM/perforce step that comes before.

          [JENKINS-27657] SCM workspace checkout for perforce can't access the ssh-agent

          David Young created issue -
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 161869 ] New: JNJira + In-Review [ 180876 ]

          Jesse Glick added a comment -

          Still reproducible? SSHAgentBuildWrapper does use preCheckout, presumably in order to support this exact use case.

          Anyway it is advisable to use Pipeline if you need fine-grained control over order of execution.

          Jesse Glick added a comment - Still reproducible? SSHAgentBuildWrapper does use preCheckout , presumably in order to support this exact use case. Anyway it is advisable to use Pipeline if you need fine-grained control over order of execution.

            Unassigned Unassigned
            dayoung David Young
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: