Jenkins 管道总是跳过 Git 标记的“when”条件的阶段

Question

在声明性多分支Jenkins管道中，我只希望在Git标记存在的情况下运行一个阶段。出于测试原因，我设置了一个简单的虚拟管道。但是，始终跳过演示阶段。我检查了Git标签是否存在，并且我也推了标签，但这似乎没有任何效果。

詹金斯文件

pipeline {
    agent any

    environment {
        APP_NAME = 'myapp'
    }

    stages {
        stage('Demo') {
            when { buildingTag() }
            steps {
                echo "Found a tag..."
            }
        }
    }
}

Jenkins构建的控制台输出

[Pipeline] }
[Pipeline] // stage
[Pipeline] withEnv
[Pipeline] {
[Pipeline] withCredentials
[Pipeline] {
[Pipeline] withEnv
[Pipeline] {
[Pipeline] stage
[Pipeline] { (Demo)
Stage "Demo" skipped due to when conditional
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] }
[Pipeline] // withCredentials
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline

克隆存储库的日志输出

 > git rev-parse --is-inside-work-tree # timeout=10
Setting origin to [e-mail]:my-project/myapp.git
 > git config remote.origin.url [e-mail]:my-project/myapp.git # timeout=10
Fetching origin...
Fetching upstream changes from origin
 > git --version # timeout=10
 > git config --get remote.origin.url # timeout=10
using GIT_SSH to set credentials 
 > git fetch --tags --progress origin +refs/heads/*:refs/remotes/origin/*
Seen branch in repository origin/master
Seen 1 remote branch
Obtained Jenkinsfile from 1bcf713882dbdba6b8007e0f6c23b44207cbab1e
Running in Durability level: MAX_SURVIVABILITY
[Pipeline] node
Running on vm-abn-jenk-002 in /var/lib/jenkins/workspace/build-myapp-app/master
[Pipeline] {
[Pipeline] stage
[Pipeline] { (Declarative: Checkout SCM)
[Pipeline] checkout
using credential 7253b0d3-b5a6-4569-a3ad-5392cba89d9b
Fetching changes from the remote Git repository
Checking out Revision 1bcf713882dbdba6b8007e0f6c23b44207cbab1e (master)
Commit message: "Update Jenkinsfile"
 > git rev-parse --is-inside-work-tree # timeout=10
 > git config remote.origin.url [e-mail]:my-project/myapp.git # timeout=10
Fetching upstream changes from [e-mail]:my-project/myapp.git
 > git --version # timeout=10
using GIT_SSH to set credentials 
 > git fetch --tags --progress [e-mail]:my-project/myapp.git +refs/heads/*:refs/remotes/origin/* --depth=1
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 1bcf713882dbdba6b8007e0f6c23b44207cbab1e
 > git rev-list --no-walk 1bcf713882dbdba6b8007e0f6c23b44207cbab1e # timeout=10

Answer 1

请注意以下几点:

查看修订版1bcf713882dbdba6b8007e0f6c23b44207cbab1e（主）

这表明代码正在检查一个分支，而不是一个标签。你需要检查一个标签来使它工作。输出将类似于:

检查版本A8 deb 8 ef 28 D4 b 83 e5f 146 AFE 132 AC 21 dee 47 f 225(测试标签)

从技术上讲，tag和buildingTag条件检查是否设置了TAG_NAME环境变量（tag还检查值）。这是在Git插件签出标签时自动设置的，但在签出分支时不可用，即使在同一个提交上有标签。

由于您似乎正在使用多分支管道，因此您需要从标签选项卡开始构建以使其正常工作。