Gitlab-plugin: NullPointerException in GitLabCommitStatusStep

Created on 26 Feb 2020 · 5Comments · Source: jenkinsci/gitlab-plugin

This bug seems to be similar to #1024 and #814 but I'm not sure if it is a duplicate.

Issue

Context

Gitlab plugin version: 1.5.13
Gitlab version: 12.8.1-ee
Jenkins version: 2.222
Job type: Pipeline

Logs & Traces

[Pipeline] End of Pipeline
java.lang.NullPointerException
    at com.dabsquared.gitlabjenkins.workflow.GitLabCommitStatusStep.access$400(GitLabCommitStatusStep.java:34)
    at com.dabsquared.gitlabjenkins.workflow.GitLabCommitStatusStep$GitLabCommitStatusStepExecution$1.onFailure(GitLabCommitStatusStep.java:110)
    at org.jenkinsci.plugins.workflow.cps.CpsBodyExecution$FailureAdapter.receive(CpsBodyExecution.java:361)
    at com.cloudbees.groovy.cps.impl.ThrowBlock$1.receive(ThrowBlock.java:68)
    at com.cloudbees.groovy.cps.impl.ConstantBlock.eval(ConstantBlock.java:21)
    at com.cloudbees.groovy.cps.Next.step(Next.java:83)
    at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:174)
    at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:163)
    at org.codehaus.groovy.runtime.GroovyCategorySupport$ThreadCategoryInfo.use(GroovyCategorySupport.java:129)
    at org.codehaus.groovy.runtime.GroovyCategorySupport.use(GroovyCategorySupport.java:268)
    at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:163)
    at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.access$001(SandboxContinuable.java:18)
    at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.run0(SandboxContinuable.java:51)
    at org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(CpsThread.java:185)
    at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:400)
    at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$400(CpsThreadGroup.java:96)
    at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:312)
    at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:276)
    at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$2.call(CpsVmExecutorService.java:67)
    at java.util.concurrent.FutureTask.run(FutureTask.java:266)
    at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:131)
    at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
    at jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutorService.java:59)
    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:1149)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    at java.lang.Thread.run(Thread.java:748)
Finished: FAILURE

Problem description

I was forced to delete all old builds (thx 'build discarder'). Now it looks like the error appears in every builds where there is no previous build (anymore).
What makes it worse than a regular failed build, is that Jenkins can't handle the error and would not remove the job from the executor. I had to manually "cancel" at least some of these failed builds.

Source

nussera

👍6

All 5 comments

We have a user 'input' without timeout and that happens each time "Proceed" is pressed after Jenkins restart.

ipleten on 1 May 2020

Could it be caused by 'transient' in https://github.com/jenkinsci/gitlab-plugin/blob/1bf706bc807051da7fc4e0843bf4e306888ff743/src/main/java/com/dabsquared/gitlabjenkins/workflow/GitLabCommitStatusStep.java#L77?

ipleten on 1 May 2020

We have a user 'input' without timeout and that happens each time "Proceed" is pressed after Jenkins restart.

It looks like we are in the exact same workflow, we also encounter this issue after a Jenkins restart when someone tries to proceed a job awaiting validation.

@ipleten Did you manage to fix this on your end without merging MR #1057 ? Or was the MR closed for another reason ?