• Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • Nexus Uploader Plugin 2.9
      workflow-step-api 2.7
      job-dsl 1.57
      credentials-plugin 2.1.11
      Jenkins 2.13

      After Updating the Pipeline Plugins and the Uploader plugin, the later plugin throws an Null-Pointer-Exception when it is executed.

      Here is the Errormessage:
      java.lang.NullPointerException
      at sp.sd.nexusartifactuploader.steps.NexusArtifactUploaderStep$Execution.run(NexusArtifactUploaderStep.java:224)
      at sp.sd.nexusartifactuploader.steps.NexusArtifactUploaderStep$Execution.run(NexusArtifactUploaderStep.java:203)
      at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:47)
      at hudson.security.ACL.impersonate(ACL.java:213)
      at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:44)
      at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
      at java.util.concurrent.FutureTask.run(FutureTask.java:266)
      at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
      at java.lang.Thread.run(Thread.java:745)

          [JENKINS-41619] NPE in Pipeline Step after update

          Suresh Kumar added a comment -

          asteffens
          Let me know from which version you have upgraded plugin to latest version and the configuration of previous version. So that I can verify the bug and if possible will release a patch once we were able to replicate the issue.

          Suresh Kumar added a comment - asteffens Let me know from which version you have upgraded plugin to latest version and the configuration of previous version. So that I can verify the bug and if possible will release a patch once we were able to replicate the issue.

          Jim Coll added a comment -

          I've also seen this issue, it's started happening after upgrading from v2.4 to v2.9

          Jim Coll added a comment - I've also seen this issue, it's started happening after upgrading from v2.4 to v2.9

          Suresh Kumar added a comment -

          From v2.8 included capability of adding multiple artifacts and there is change in the configuration, we have to reconfigure the build step after upgrading.

          Suresh Kumar added a comment - From v2.8 included capability of adding multiple artifacts and there is change in the configuration, we have to reconfigure the build step after upgrading.

          I had the same issue with v2.9. Downgrading to v2.7 worked for me by now.

          Stefan Callsen added a comment - I had the same issue with v2.9. Downgrading to v2.7 worked for me by now.

            pskumar448 Suresh Kumar
            asteffens Andreas Steffens
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: