Re: Any idea why a TaskListenerDecorator could cause logger.println() to throw null pointer exception

2019-04-17 Thread Jesse Glick
On Wed, Apr 17, 2019 at 11:53 AM Daniel Anechitoaie wrote: > What's strange is that if I use sh() step it works ok. Isn't sh step also > executing on the slave? Yes but traditionally the _output_ was processed on the master not the agent. That is still true by default, pending JENKINS-52165

Re: Any idea why a TaskListenerDecorator could cause logger.println() to throw null pointer exception

2019-04-17 Thread Matt Sicker
Latest release is 3.42: https://github.com/jenkinsci/plugin-pom/releases On Wed, Apr 17, 2019 at 10:53 AM Daniel Anechitoaie wrote: > > What's strange is that if I use sh() step it works ok. Isn't sh step also > executing on the slave? > > So this works fine: > > --- > node { >

Re: Any idea why a TaskListenerDecorator could cause logger.println() to throw null pointer exception

2019-04-17 Thread Daniel Anechitoaie
What's strange is that if I use sh() step it works ok. Isn't sh step also executing on the slave? So this works fine: --- node { stage('Test') { withCodeReviewAssistantGitHubCheckRun(args) { sh('ls -alh') } } } --- On Wednesday, April 17, 2019 at 6:47:49 PM

Re: Any idea why a TaskListenerDecorator could cause logger.println() to throw null pointer exception

2019-04-17 Thread Daniel Anechitoaie
I'm using org.jenkins-ci.plugins plugin 3.6 Is this the latest parent POM? I'm not sure how to check which is the latest version available. On Wednesday, April 17, 2019 at 6:09:07 PM UTC+3, Jesse Glick wrote: > > On Wed, Apr 17, 2019 at 10:47 AM Daniel Anechitoaie > >

Re: Any idea why a TaskListenerDecorator could cause logger.println() to throw null pointer exception

2019-04-17 Thread Jesse Glick
On Wed, Apr 17, 2019 at 10:47 AM Daniel Anechitoaie wrote: > So I think the problem might be with serialization and they way I try to > capture data in TaskListenerDecorator Probably. You should not be attempting to serialize a `StepExecution` there; it can only be saved in `program.dat`,

Re: Any idea why a TaskListenerDecorator could cause logger.println() to throw null pointer exception

2019-04-17 Thread Daniel Anechitoaie
Nope. I'm still getting NullPointerException even with getContext().newBodyInvoker() .withContexts(environmentExpander, taskListenerDecorator) .withCallback(BodyExecutionCallback.wrap(getContext())) .start(); So something else must be the issue but not sure what. On Wednesday, April 17,

Re: Any idea why a TaskListenerDecorator could cause logger.println() to throw null pointer exception

2019-04-17 Thread Daniel Anechitoaie
I suspect my problem is with .withCallback(new WithCheckRunStepExecutionCallback(this)) ? But then if I use ".withCallback(BodyExecutionCallback.wrap(getContext()))" instead, how will I be able to read a variable from within StepExecution class? On Wednesday, April 17, 2019 at 4:18:28 PM

Any idea why a TaskListenerDecorator could cause logger.println() to throw null pointer exception

2019-04-17 Thread Daniel Anechitoaie
I have a pipeline step plugin that wraps other steps and captures the output and for some reason this causes a Null Pointer Exception when I try to do logger.println() from the step plugin that is wrapped. *So with this pipeline:* --- node { stage('Test') {