Details
-
Type:
Bug
-
Status: Resolved (View Workflow)
-
Priority:
Minor
-
Resolution: Fixed
-
Component/s: support-core-plugin
-
Labels:
-
Environment:support-core-2.56
-
Similar Issues:
-
Released As:support-core-2.58
Description
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
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)
Attachments
Issue Links
- is duplicated by
-
JENKINS-58880 NPE from support core plugin attaching bundle
-
- Closed
-
- links to
I think we should check if this also reproducible out of JCasC configured.
At this stage, Oleg is saying it looks only like log spam, but we'd need to double check.