I have a node which has been configured with JCasC and then never connected. When Support Core Plugin generates a bundle, I see NPE in System logs.
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)
I have a node which has been configured with JCasC and then never connected. When Support Core Plugin generates a bundle, I see NPE in System logs.
Acceptance criteria: * There is handling of null inputs in the reporting path
Nice 2 have: * Methods are annotated to ensure that there is no such mistakes happening in the future
{code:java}
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)
It only happens with JCasC because the node configured ha the field to null instead of "" (empty string). Not sure whether it's a bug in JCasC or not because the field is mandatory anyway. Why can you leave it empty in the UI?
If we consider that JCasC should do the same as the UI then it's a bug in the UI.
It only happens with JCasC because the node configured ha the field to *null* instead of *""* (empty string). Not sure whether it's a bug in JCasC or not because the field is mandatory anyway. Why can you leave it empty in the UI?
If we consider that JCasC should do the same as the UI then it's a bug in the UI.