使用脚本管道将 sonarqube 与 jenkins 集成时出现错误 "Unknown stage section"

Error "Unknown stage section" while integrating sonarqube with jenkins using scripted pipeline

我一直在尝试将 sonarqube 与 Jenkins 集成。它工作正常,直到我使用脚本化管道 return 质量门状态。 我写的代码是:

pipeline {
agent any
stages {
    stage("Git checkout") {
        steps {
            git 'https://github.com/AmolMandloi/junit-java-example.git'
        }
    }
    stage("Maven") {
        steps {
            bat "mvn clean package test"
        }
    }
    stage("Sonar") {
        steps {
withSonarQubeEnv('sonar'){
        bat 'mvn sonar:sonar'
    }
        }
    }
    stage("Quality Gate"){
        timeout(time: 1, unit: 'HOURS') {
            def qg = waitForQualityGate()
            if (qg.status != 'OK') {
                error "Pipeline aborted due to quality gate failure: ${qg.status}"
          }
      }
  }
    stage("Postsonar") {
        steps{
            bat 'echo "All done"'
        }
    }

}}

错误出现在质量门阶段,因为没有它一切正常。enter image description here

这是错误:

由用户 Amol Mandloi 发起 运行 耐久等级:MAX_SURVIVABILITY org.codehaus.groovy.control.MultipleCompilationErrorsException:启动失败: WorkflowScript:21:未知阶段部分 "timeout"。从 0.5 版开始,阶段中的步骤必须在“步骤”块中。 @ 第 21 行,第 9 列。 舞台("Quality Gate"){ ^

WorkflowScript:21:阶段 "Quality Gate" @ 第 21 行第 9 列的预期 "steps"、"stages" 或 "parallel" 之一。 舞台("Quality Gate"){ ^

2 个错误

at org.codehaus.groovy.control.ErrorCollector.failIfErrors(ErrorCollector.java:310)
at org.codehaus.groovy.control.CompilationUnit.applyToPrimaryClassNodes(CompilationUnit.java:1085)
at org.codehaus.groovy.control.CompilationUnit.doPhaseOperation(CompilationUnit.java:603)
at org.codehaus.groovy.control.CompilationUnit.processPhaseOperations(CompilationUnit.java:581)
at org.codehaus.groovy.control.CompilationUnit.compile(CompilationUnit.java:558)
at groovy.lang.GroovyClassLoader.doParseClass(GroovyClassLoader.java:298)
at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:268)
at groovy.lang.GroovyShell.parseClass(GroovyShell.java:688)
at groovy.lang.GroovyShell.parse(GroovyShell.java:700)
at org.jenkinsci.plugins.workflow.cps.CpsGroovyShell.doParse(CpsGroovyShell.java:142)
at org.jenkinsci.plugins.workflow.cps.CpsGroovyShell.reparse(CpsGroovyShell.java:127)
at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.parseScript(CpsFlowExecution.java:561)
at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.start(CpsFlowExecution.java:522)
at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:337)
at hudson.model.ResourceController.execute(ResourceController.java:97)
at hudson.model.Executor.run(Executor.java:428)

已完成:失败

stage("Quality Gate"){
    timeout(time: 1, unit: 'HOURS') {
        def qg = waitForQualityGate()
        if (qg.status != 'OK') {
            error "Pipeline aborted due to quality gate failure: ${qg.status}"
        }
    }
}

在声明式管道中,timeout 直接在 stage 下无效。您可以将其用作 选项 步骤 .

在任何情况下,声明性管道中的脚本部分都需要 script 步骤。

超时选项

stage("Quality Gate"){
    options {
        timeout(time: 1, unit: 'HOURS') 
    }
    steps {
        script {
            def qg = waitForQualityGate()
            if (qg.status != 'OK') {
                error "Pipeline aborted due to quality gate failure: ${qg.status}"
        }
    }
}

当超时应用于阶段中的所有内容时,此语法更具可读性。

超时步骤

stage("Quality Gate"){
    steps {
        script {
            timeout(time: 1, unit: 'HOURS') {
                def qg = waitForQualityGate()
                if (qg.status != 'OK') {
                    error "Pipeline aborted due to quality gate failure: ${qg.status}"
            }
        }
    }
}

当超时仅适用于部分阶段时,此语法是必需的。在你的情况下,我会选择 timeout 选项以获得更具声明性、可读性的方法。