[JIRA] (JENKINS-41619) NPE in Pipeline Step after update

1 view
Skip to first unread message

info@andreas-steffens.de (JIRA)

unread,
Feb 1, 2017, 5:53:02 AM2/1/17
to jenkinsc...@googlegroups.com
Andreas Steffens created an issue
 
Jenkins / Bug JENKINS-41619
NPE in Pipeline Step after update
Issue Type: Bug Bug
Assignee: Suresh Kumar
Components: nexus-artifact-uploader-plugin
Created: 2017/Feb/01 10:52 AM
Environment: Nexus Uploader Plugin 2.9
workflow-step-api 2.7
job-dsl 1.57
credentials-plugin 2.1.11
Jenkins 2.13
Priority: Major Major
Reporter: Andreas Steffens

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)

Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
Atlassian logo

pskumar448@gmail.com (JIRA)

unread,
Feb 5, 2017, 10:38:04 PM2/5/17
to jenkinsc...@googlegroups.com
Suresh Kumar commented on Bug JENKINS-41619
 
Re: NPE in Pipeline Step after update

Andreas Steffens
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.

colljim@gmail.com (JIRA)

unread,
Feb 21, 2017, 12:43:01 PM2/21/17
to jenkinsc...@googlegroups.com
Jim Coll commented on Bug JENKINS-41619

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

pskumar448@gmail.com (JIRA)

unread,
Feb 21, 2017, 10:18:01 PM2/21/17
to jenkinsc...@googlegroups.com

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.

Reply all
Reply to author
Forward
0 new messages