基于严重性[blocker / critical / major]而不基于Type [bugs / vulnerability / code-smells]的声纳Qualitygate api

问题描述 投票:0回答:1

我正在基于analysisId从管道中点击声纳api(api / qualitygates / project_status?analysisId = xyz)以获取项目状态。收到的响应基于Type[bugs/vulnerability/code-smells]

是否可以基于Severity [blocker/critical/major]获得状态?

{
  "projectStatus": {
    "status": "ERROR",
    "conditions": [
      {
        "status": "OK",
        "metricKey": "bugs",
        "comparator": "GT",
        "errorThreshold": "0",
        "actualValue": "0"
      },
      {
        "status": "ERROR",
        "metricKey": "vulnerabilities",
        "comparator": "GT",
        "errorThreshold": "0",
        "actualValue": "31"
      },
      {
        "status": "ERROR",
        "metricKey": "code_smells",
        "comparator": "GT",
        "errorThreshold": "0",
        "actualValue": "72"
      }
    ],
    "periods": [

    ],
    "ignoredConditions": false
  }
}
jenkins sonarqube jenkins-pipeline jenkins-plugins static-analysis
1个回答
0
投票

这里我是如何获得此身份的,可能会帮助在此问题上苦苦挣扎的人。

使用短命branch-name而不是在以下api-上使用analysisId的窍门]

http://sonardashboard.xxx.com/api/issues/search?componentRoots=<Project-key>&severities=<Type of severity>&branch=<short-lived branch name>

注意:这会带来状态问题-打开和关闭。无法根据状态使用api过滤掉。

© www.soinside.com 2019 - 2024. All rights reserved.