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

Nullpointer on BasicSSHUserPrivateKey passphrase

      Hi,

      When running the same script as mentioned in this ticket: JENKINS-34653, I've got a new NullPointerException.

      It looks like the passphrase field in the following file remains null while it actually should contain the password from the credentials.
      https://github.com/jenkinsci/ssh-credentials-plugin/blob/384a93e3c188a1b01b1d92279bd5426dabb4e5ee/src/main/java/com/cloudbees/jenkins/plugins/sshcredentials/impl/BasicSSHUserPrivateKey.java

      In the script the variable credentials.passphrase is null and therefore invoking credentials.passphrase.plainText will result in a nullpointer.

      The question is, why does credentials.passphrase remain null?

      java.lang.NullPointerException: Cannot get property 'plainText' on null object
      	at org.codehaus.groovy.runtime.NullObject.getProperty(NullObject.java:60)
      	at org.codehaus.groovy.runtime.InvokerHelper.getProperty(InvokerHelper.java:174)
      	at org.codehaus.groovy.runtime.callsite.NullCallSite.getProperty(NullCallSite.java:47)
      	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callGetProperty(AbstractCallSite.java:296)
      	at Script1.run(Script1.groovy:34)
      

          [JENKINS-42280] Nullpointer on BasicSSHUserPrivateKey passphrase

          This is important for automating credentials management via tools like Chef and Puppet.

          See https://github.com/chef-cookbooks/jenkins/issues/561 for an example of the impact.

          Christian Höltje added a comment - This is important for automating credentials management via tools like Chef and Puppet. See https://github.com/chef-cookbooks/jenkins/issues/561  for an example of the impact.

          Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA

          Stephen Connolly added a comment - Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA

            Unassigned Unassigned
            borisroman Boris Schrijver
            Votes:
            8 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated: