jenkines陷入声纳-qube分析.分析和成功,但工作卡住了



我在Jenkins作业中运行声纳。分析阶段成功结束,但在此之后,作业卡住了,日志中没有任何内容,但几分钟后,我取出内存错误,作业失败。

my sonar property file:

sonar.language=javascript
# sources
sonar.sources=src
sonar.exclusions=**/node_modules/**
# tests
sonar.tests=src
sonar.test.inclusions=**/*.test.js
# tests reports
sonar.testExecutionReportPaths=reports/test-reporter.xml
sonar.javascript.lcov.reportPaths=coverage/lcov.info
sonar.verbose=true

日志:

13:31:10  13:31:10.683 INFO: Analysis report generated in 522ms, dir size=4 MB
13:31:12  13:31:12.797 INFO: Analysis report compressed in 2114ms, zip size=2 MB
13:31:12  13:31:12.797 INFO: Analysis report generated in /my_reports_loc
13:31:12  13:31:12.797 DEBUG: Upload report
13:31:12  13:31:12.955 DEBUG: POST 200 http://my-sonar/api/ce/submit?projectKeymyProjt&projectName=projectNamet | time=157ms
13:31:12  13:31:12.958 INFO: Analysis report uploaded in 161ms
13:31:12  13:31:12.959 DEBUG: Report metadata written to /my_reports_loc
13:31:12  13:31:12.959 INFO: ANALYSIS SUCCESSFUL, you can browse http://my-sonar/dashboard?id=my-project
13:31:12  13:31:12.959 INFO: Note that you will be able to access the updated dashboard once the server has processed the submitted analysis report
13:31:12  13:31:12.959 INFO: More about the report processing at http://my-sonar/api/ce/task?id=my_id
13:31:12  13:31:12.964 DEBUG: eslint-bridge server will shutdown
13:31:13  13:31:13.208 DEBUG: stylelint-bridge server will shutdown
13:31:13  13:31:13.209 INFO: Analysis total time: 42.940 s
13:31:13  13:31:13.230 INFO: ------------------------------------------------------------------------
13:31:13  13:31:13.230 INFO: EXECUTION SUCCESS
13:31:13  13:31:13.230 INFO: ------------------------------------------------------------------------
13:31:13  13:31:13.230 INFO: Total time: 44.469s
13:31:13  13:31:13.369 INFO: Final Memory: 43M/1106M
13:31:13  13:31:13.369 INFO: ------------------------------------------------------------------------
[Pipeline] }
[Pipeline] // 
[Pipeline] }
[Pipeline] // 
13:33:47 java.lang.OutOfMemoryError: GC overhead limit exceeded
Finished: FAILURE

您需要增加堆大小。

关于GC开销的错误意味着Jenkins在垃圾收集中出现了抖动。这意味着它花在垃圾收集上的时间可能比做有用的工作要多。当堆对于应用程序来说太小时,通常会出现这种情况。

这篇文章将帮助你,如果你需要知道,如何增加帮助大小的jenkins。

最新更新