Sonarqube跑步者在TeamCity跑步中退出,退出代码138

Sonarqube跑步者在TeamCity跑步中退出,退出代码138,teamcity,Teamcity,我正在将当前堆栈迁移到Teamcity,sonarqube构建步骤突然失败,输出如下: [09:56:54][Step 2/3] 09:56:54.862 INFO - Sensor SCM Sensor [09:56:54][Step 2/3] 09:56:54.872 INFO - SCM provider for this project is: hg <analysis> [09:58:28][Step 2/3] 09:58:28.921 INFO - 1197/183

我正在将当前堆栈迁移到Teamcity,sonarqube构建步骤突然失败,输出如下:

[09:56:54][Step 2/3] 09:56:54.862 INFO  - Sensor SCM Sensor
[09:56:54][Step 2/3] 09:56:54.872 INFO  - SCM provider for this project is: hg
<analysis>
[09:58:28][Step 2/3] 09:58:28.921 INFO  - 1197/1831 files analyzed
[09:58:28][Step 2/3] 09:58:28.921 WARN  - Missing blame information for the following files:
[09:58:28][Step 2/3] 09:58:28.921 WARN  -   * <list of paths>
...
[09:58:29][Step 2/3] 09:58:29.024 WARN  - This may lead to missing/broken features in SonarQube
[09:58:30][Step 2/3] INFO: ------------------------------------------------------------------------
[09:58:30][Step 2/3] INFO: EXECUTION FAILURE
[09:58:30][Step 2/3] INFO: ------------------------------------------------------------------------
[09:58:30][Step 2/3] Total time: 3:27.871s
[09:58:30][Step 2/3] Final Memory: 18M/161M
[09:58:30][Step 2/3] INFO: ------------------------------------------------------------------------
[09:58:30][Step 2/3] ERROR: Error during Sonar runner execution
[09:58:30][Step 2/3] ERROR: Unable to execute Sonar
[09:58:30][Step 2/3] ERROR: Caused by: -1
[09:58:30][Step 2/3] ERROR: 
[09:58:30][Step 2/3] ERROR: To see the full stack trace of the errors, re-run SonarQube Runner with the -e switch.
[09:58:30][Step 2/3] ERROR: Re-run SonarQube Runner using the -X switch to enable full debug logging.
[09:58:30][Step 2/3] Process exited with code 1
[09:58:30][Step 2/3] Step SonarQube Runner failed
[09:56:54][Step 2/3]09:56:54.862信息-传感器SCM传感器
[09:56:54][Step 2/3]09:56:54.872信息-本项目的供应链供应商为:hg
[09:58:28][Step 2/3]09:58:28.921信息-已分析1197/1831个文件
[09:58:28][步骤2/3]09:58:28.921警告-缺少以下文件的责任信息:
[09:58:28][Step 2/3]09:58:28.921警告-*
...
[09:58:29][Step 2/3]09:58:29.024警告-这可能导致SonarQube中的功能缺失/损坏
[09:58:30][Step 2/3]信息:------------------------------------------------------------------------
[09:58:30][Step 2/3]信息:执行失败
[09:58:30][Step 2/3]信息:------------------------------------------------------------------------
[09:58:30][Step 2/3]总时间:3:27.871s
[09:58:30][Step 2/3]最终内存:18M/161M
[09:58:30][Step 2/3]信息:------------------------------------------------------------------------
[09:58:30][Step 2/3]错误:在执行Sonar runner时出错
[09:58:30][Step 2/3]错误:无法执行声纳
[09:58:30][步骤2/3]错误:由以下原因引起:-1
[09:58:30][Step 2/3]错误:
[09:58:30][Step 2/3]错误:要查看错误的完整堆栈跟踪,请使用-e开关重新运行SonarQube Runner。
[09:58:30][Step 2/3]错误:使用-X开关重新运行SonarQube Runner以启用完全调试日志记录。
[09:58:30][步骤2/3]进程已退出,代码为1
[09:58:30][Step 2/3]Step SonarQube Runner失败

我如何克服这个问题,使构建继续进行,或者至少获得构建失败的确切原因?Mercurial数据目录(.hg)应该在适当的位置,签出在代理端完成。

我可以通过禁用Sonarqube中的scm传感器来抑制错误,但这有点像是在你的技术债务鞋上放了一块石头。你试着按照它的建议做了吗?@MichaelHampton不,我不熟悉runner,我甚至不知道它在teamcity结构中的位置,也不知道如何重现相同的环境。我真正困惑的是:为什么你认为这是一个ops问题?@MichaelHampton我总是困惑我的问题应该放在哪里——服务器故障、超级用户,等等——但我认为这是三个问题中最接近的一个(如果我错了,请纠正我,如果您认为正确,请随意将问题转移到其他地方)