[ 
https://issues.jenkins-ci.org/browse/JENKINS-13722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163170#comment-163170
 ] 

SCM/JIRA link daemon commented on JENKINS-13722:
------------------------------------------------

Code changed in jenkins
User: Jason Swager
Path:
 src/main/java/org/jenkinsci/plugins/vSphereCloudRunListener.java
http://jenkins-ci.org/commit/vsphere-cloud-plugin/cd25ecd19ffde72eb6b8d9411ca968b10e1f4f76
Log:
  JENKINS-13722: Fixed problem that broke unrelated matrix builds.





                
> vSphere plugin causing non-vSphere jobs to fail
> -----------------------------------------------
>
>                 Key: JENKINS-13722
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13722
>             Project: Jenkins
>          Issue Type: Bug
>          Components: vsphere-cloud
>            Reporter: Christian Höltje
>              Labels: slave
>
> I have vSphere plugin 0.9 and Jenkins 1.462 (and I tried 1.463) and it caused 
> matrix jobs, that do not run on vSphere slaves, to die with this error:
> Started by timer
> FATAL: null
> java.lang.NullPointerException
>       at 
> org.jenkinsci.plugins.vSphereCloudRunListener.onStarted(vSphereCloudRunListener.java:32)
>       at hudson.model.listeners.RunListener.fireStarted(RunListener.java:188)
>       at hudson.model.Run.run(Run.java:1429)
>       at hudson.matrix.MatrixBuild.run(MatrixBuild.java:248)
>       at hudson.model.ResourceController.execute(ResourceController.java:88)
>       at hudson.model.Executor.run(Executor.java:239)
>       at hudson.model.OneOffExecutor.run(OneOffExecutor.java:66)
> To add insult to injury, the builds then got locked. :-(
> None of the vSphere slaves seemed to be having problems (in fact, jobs were 
> building on them just fine).
> My solution was to change all my vSphere slaves to normal slaves and then 
> removing the plugin. Simply changing the slaves  wasn't enough.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


Reply via email to