jenkins多分支管道中的分支索引触发了额外的构建，这已经由轮询SCM构建

Question

我有一个多分支管道。我已在Jenkins文件属性中配置触发器：

pipelineTriggers([pollSCM('H/2 * * * *')])])

多分支管道配置为定期"扫描多分支管道触发器"。预期行为：触发器仅构建在通过jenkinsFile实际配置的构建触发器上：它触发在轮询SCM和相同提交的“重新索引”上的构建。

我们正在使用

詹金斯：2.107.1

git插件： 3.8.0

管道多分支： 2.17

Answer 1

我想我们无法阻止构建触发器进行扫描。但是我们的构建应该能够识别并停止额外的构建。

// execute this before anything else, including requesting any time on an agent
    if (currentBuild.getBuildCauses().toString().contains('BranchIndexingCause')) {
      print "INFO: Build skipped due to trigger being Branch Indexing"
      currentBuild.result = 'ABORTED' // optional, gives a better hint to the user that it's been skipped, rather than the default which shows it's successful
      return
    }

来源：https://www.jvt.me/posts/2020/02/23/jenkins-multibranch-skip-branch-index/