-
Bug
-
Resolution: Won't Fix
-
Minor
-
None
-
Jenkins 2.235.4 with text-finder 1.15 using a job that was originally created with text-finder 1.12
I have a job defined with text-finder 1.12 settings to mark the build unstable if the text was found in the console log. When I run that job with text-finder 1.15, a null pointer exception is reported like this:
BUILD SUCCESSFUL Total time: 0 seconds ERROR: Build step failed with exception java.lang.NullPointerException at hudson.plugins.textfinder.TextFinderPublisher.perform(TextFinderPublisher.java:248) at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:78) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:741) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:690) at hudson.model.Build$BuildExecution.post2(Build.java:186) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:635) at hudson.model.Run.execute(Run.java:1905) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:428) Build step 'Search files or the console log for regular expression(s)' marked build as failure Finished: FAILURE
If I save the job and run it again it succeeds. Since the workaround is so simple, I don't know that this is worth any time to fix it. I'm submitting the issue to document it just in case others encounter the same issue.