We only run jobs on slaves and the master has no executors, so would this code 
not reliably hit this issue if it was a master/slave issue?

/James

From: [email protected] [mailto:[email protected]] On 
Behalf Of Christoph Kutzinski
Sent: 30 January 2013 11:55
To: [email protected]
Subject: Aw: Plugin can't find its own descriptor?

I'm not sure but maybe the code part where you are is running in the forked 
Java VM for the Maven build where the descriptors would be null - AFAIK.

You need to do your work in a callable which executes the code on the master.
Gesendet: Mittwoch, 30. Januar 2013 um 12:49 Uhr
Von: "James Nord (jnord)" <[email protected]<mailto:[email protected]>>
An: "[email protected]<mailto:[email protected]>" 
<[email protected]<mailto:[email protected]>>
Betreff: Plugin can't find its own descriptor?
Hi all,

I got a really bizarre stacktrace from my plugin overnight (m2release 0.9.1, 
Jenkins 1.466.2+JENKINS-15382).

ERROR: Processing failed due to a bug in the code. Please report this to 
[email protected]<mailto:[email protected]>
java.lang.NullPointerException
  at 
hudson.model.AbstractDescribableImpl.getDescriptor(AbstractDescribableImpl.java:35)
  at 
org.jvnet.hudson.plugins.m2release.M2ReleaseBuildWrapper.getDescriptor(M2ReleaseBuildWrapper.java:395)
  at 
org.jvnet.hudson.plugins.m2release.M2ReleaseBuildWrapper$2.tearDown(M2ReleaseBuildWrapper.java:234)
  at 
hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:817)
  at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:480)
  at hudson.model.Run.run(Run.java:1438)
  at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:477)
  at hudson.model.ResourceController.execute(ResourceController.java:88)
  at hudson.model.Executor.run(Executor.java:239)

But this occurs at the end of the job during the plugin environments teardown

But what I don't understand is how the plugin can be used in a job if its main 
descriptor can't be found, and this was a once off as subsequent releases are 
fine...

Anyone any clues - is there any know issues in core around this area?

/James
--
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
[email protected]<mailto:[email protected]>.
For more options, visit https://groups.google.com/groups/opt_out.



--
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
[email protected]<mailto:[email protected]>.
For more options, visit https://groups.google.com/groups/opt_out.


-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to