jenkins - Findbugs java 结果 : 137 static analysis plugin

Question

每次提交后，我们都会在 jenkins 上运行 findbug 作业，其结果由静态分析插件发布。这通常完全按照预期工作，但是有时(大约每 100 个构建一次)findbugs 会以退出代码 137 退出。当它这样做时，也会生成一个完全空的 findbugs.xml 文件

空的 xml 文件导致静态分析插件认为这个构建真的很棒(没有错误)，并将其用作新的引用构建，这反过来又使之后的每个构建失败/不稳定。

我真的找不到任何关于此退出代码的含义或如何防止它的有用信息。我正在寻找一种方法来防止出现此退出代码 137 或让静态分析插件将此构建视为失败(而不是新的引用构建)

我还想知道这段代码的实际含义。

作业的控制台输出，退出代码为 137(作业:#1957，报告没有错误)

--- snip -- more applying of bugpatterns--
[findbugs] Applying edu.umd.cs.findbugs.detect.MultithreadedInstanceAccess to nl/base/rela/entities/relagroups/RelationGroup$1
 [findbugs] Applying edu.umd.cs.findbugs.detect.BadUseOfReturnValue to nl/base/rela/entities/relagroups/RelationGroup$1
 [findbugs] Applying edu.umd.cs.findbugs.detect.MethodReturnCheck to nl/base/rela/entities/relagroups/RelationGroup$1
 [findbugs] Applying edu.umd.cs.findbugs.detect.IDivResultCastToDouble to nl/base/rela/entities/relagroups/RelationGroup$1
 [findbugs] Applying edu.umd.cs.findbugs.detect.FindBadCast2 to nl/base/rela/entities/relagroups/RelationGroup$1
 [findbugs] Java Result: 137
 [findbugs] Output saved to findbugs.xml

BUILD SUCCESSFUL
Total time: 9 minutes 0 seconds
[FINDBUGS] Collecting findbugs analysis files...
[FINDBUGS] Finding all files that match the pattern trunk/findbugs.xml
[FINDBUGS] Parsing 1 files in /data/hudson/workspace/crm-findbugs
[FINDBUGS] Skipping file  of module /data/hudson/workspace/crm-findbugs/trunk/findbugs.xml because it's empty.
[FINDBUGS] Computing warning deltas based on reference build #1956
[ANALYSIS-COLLECTOR] Computing warning deltas based on reference build #1956
Archiving artifacts

上一个作业的控制台输出(作业:#1956，报告现有错误):

     ---snip---
 [findbugs] Applying edu.umd.cs.findbugs.detect.AtomicityProblem to nl/base/rela/entities/Project$1
 [findbugs] Applying edu.umd.cs.findbugs.detect.DefaultEncodingDetector to nl/base/rela/entities/Project$1
 [findbugs]       32 usecs/byte      29 msec     898 bytes  1 pass nl/base/rela/entities/Project$1
 [findbugs] Analysis completed
 [findbugs] Warnings generated: 770
 [findbugs] Calculating exit code...
 [findbugs] Setting 'bugs found' flag (1)
 [findbugs] Exit code set to: 1
 [findbugs] Java Result: 1
 [findbugs] Output saved to findbugs.xml

BUILD SUCCESSFUL
Total time: 9 minutes 30 seconds
[FINDBUGS] Collecting findbugs analysis files...
[FINDBUGS] Finding all files that match the pattern trunk/findbugs.xml
[FINDBUGS] Parsing 1 files in /data/hudson/workspace/crm-findbugs
[FINDBUGS] Successfully parsed file /data/hudson/workspace/crm-findbugs/trunk/findbugs.xml of module  with 770 warnings.
[FINDBUGS] Computing warning deltas based on reference build #1955
[ANALYSIS-COLLECTOR] Computing warning deltas based on reference build #1955
Archiving artifacts

Answer 1

1. 作为解决方法，添加 buld 步骤来运行脚本，检查 findbugs.xml 文件是否为空，如果为空则返回非零退出代码，导致构建失败

2. 针对 Jenkins 插件提交错误报告 https://issues.jenkins-ci.org

3. 可选:检查插件，自行修复，提交补丁