-
Bug
-
Resolution: Fixed
-
Minor
-
None
I encountered a support core null pointer exception while evaluating other things.
The null pointer exception stack trace was:
Aug 09, 2019 7:16:52 PM com.cloudbees.jenkins.support.SupportPlugin writeBundle
WARNING: Could not attach ''nodes.md'' to support bundle
java.lang.NullPointerException
at com.cloudbees.jenkins.support.util.Markdown.escapeBacktick(Markdown.java:17)
at com.cloudbees.jenkins.support.impl.AboutJenkins$NodesContent.printTo(AboutJenkins.java:877)
at com.cloudbees.jenkins.support.api.PrintedContent.writeTo(PrintedContent.java:56)
at com.cloudbees.jenkins.support.SupportPlugin.writeBundle(SupportPlugin.java:316)
at com.cloudbees.jenkins.support.SupportPlugin.writeBundle(SupportPlugin.java:278)
at com.cloudbees.jenkins.support.SupportPlugin$PeriodicWorkImpl.lambda$doRun$0(SupportPlugin.java:820)
at java.lang.Thread.run(Thread.java:748)
- duplicates
-
-
- Resolved
-
[JENKINS-58880] NPE from support core plugin attaching bundle
As far as I can tell, I'm running support-core plugin 2.56 as contained in CJD 2.176.2.3 release 2.
allan_burdajewicz I was preparing for a Jenkins World 2019 talk on Docker and Jenkins [as code] and found it while working on a pull request based on https://github.com/cloudbees-oss/cjd-jcasc-demo/tree/8909603c0befb598d90e5e1c316354040a5552eb . I was running in a Docker container using Docker for Windows (Linux container running on a Windows computer) using the changes in my proposed pull request https://github.com/cloudbees-oss/cjd-jcasc-demo/pull/9 .
During startup, the console output reports that null pointer exception.
Allan BURDAJEWICZ
added a comment - CJD 2.176.2.3 ships with 2.56 indeed. So I assume this is fixed in 2.58. Let me try to reproduce the issue to confirm that.
Allan BURDAJEWICZ
added a comment - CJD 2.176.2.3 ships with 2.56 indeed. So I assume this is fixed in 2.58. Let me try to reproduce the issue to confirm that. Allan BURDAJEWICZ
added a comment - Confirmed that:
- this is caused by the missing remoteFS for those 2 agents: https://github.com/cloudbees-oss/cjd-jcasc-demo/blob/1.3/jenkins.yaml#L82-L107
- support-core:2.58 fixes this
Note: The remote FS is a mandatory field field in the UI but for not from JCasC. Although resiliency has been added to the support-core plugin in that regards, this could well be a bug with JCasC as suggested in https://github.com/jenkinsci/support-core-plugin/pull/179#issuecomment-510910195 ?
Allan BURDAJEWICZ
added a comment - Confirmed that:
this is caused by the missing remoteFS for those 2 agents: https://github.com/cloudbees-oss/cjd-jcasc-demo/blob/1.3/jenkins.yaml#L82-L107
support-core:2.58 fixes this
Note: The remote FS is a mandatory field field in the UI but for not from JCasC. Although resiliency has been added to the support-core plugin in that regards, this could well be a bug with JCasC as suggested in https://github.com/jenkinsci/support-core-plugin/pull/179#issuecomment-510910195 ? 
markewaite What version of support-core are you running ? I am pretty sure this is fixed in version 2.58, addressed by
JENKINS-57602.