[JIRA] (JENKINS-58751) TAG_NAME is not populated in declarative multibranch pipeline
Title: Message Title John Doe commented on JENKINS-58751 Re: TAG_NAME is not populated in declarative multibranch pipeline Yes, thank you, you're assumptions are mostly correct. It turned out the problem is that 'TAG_NAME' is only populated when the build is triggered because of a tag. In order to get builds triggered by tags one needs the Basic Branch Build Strategies plugin (https://wiki.jenkins.io/display/JENKINS/Basic+Branch+Build+Strategies+Plugin). I think the docs on the when condition (https://jenkins.io/doc/book/pipeline/syntax/#when) could be improved upon by mentioning this. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201054.1564649736000.6591.1564749960092%40Atlassian.JIRA.
[JIRA] (JENKINS-58751) TAG_NAME is not populated in declarative multibranch pipeline
Title: Message Title John Doe updated an issue Jenkins / JENKINS-58751 TAG_NAME is not populated in declarative multibranch pipeline Change By: John Doe Component/s: declarative-pipeline-when-conditions-plugin Component/s: git-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201054.1564649736000.6585.1564749721097%40Atlassian.JIRA.
[JIRA] (JENKINS-58751) TAG_NAME is not populated in declarative multibranch pipeline
Title: Message Title John Doe updated an issue Jenkins / JENKINS-58751 TAG_NAME is not populated in declarative multibranch pipeline Change By: John Doe Issue Type: Bug Improvement Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201054.1564649736000.6584.1564749721082%40Atlassian.JIRA.
[JIRA] (JENKINS-58751) TAG_NAME is not populated in descriptive multibranch pipeline
Title: Message Title
John Doe created an issue
Jenkins / JENKINS-58751
TAG_NAME is not populated in descriptive multibranch pipeline
Issue Type:
Bug
Assignee:
Mark Waite
Components:
git-plugin
Created:
2019-08-01 08:55
Environment:
Windows 10, Jenkins ver. 2.176.2
Labels:
when tag git declarative-pipeline
Priority:
Major
Reporter:
John Doe
I configured a multibranch pipeline to check out via git, discover branches, discover tags and the added clone behaviour to fetch tags. However I can't use the when condition with tags as outlined here (https://jenkins.io/blog/2018/05/16/pipelines-with-git-tags/). According to the docs (https://jenkins.io/doc/book/pipeline/syntax/#when) when depends on the variable TAG_NAME which I assume should be set by Jenkins. But both params.TAG_NAME, env.TAG_NAME are null. Thus my when condition 'when { tag "" }' never triggers.
