[JIRA] (JENKINS-58751) TAG_NAME is not populated in declarative multibranch pipeline
Title: Message Title Mark Waite updated JENKINS-58751 Jenkins / JENKINS-58751 TAG_NAME is not populated in declarative multibranch pipeline Change By: Mark Waite Status: Open Fixed but Unreleased Resolution: Not A Defect 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.7236.1564837800304%40Atlassian.JIRA.
[JIRA] (JENKINS-58751) TAG_NAME is not populated in declarative multibranch pipeline
Title: Message Title Mark Waite updated JENKINS-58751 Jenkins / JENKINS-58751 TAG_NAME is not populated in declarative multibranch pipeline Change By: Mark Waite Status: Fixed but Unreleased Closed 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.7238.1564837800328%40Atlassian.JIRA.
[JIRA] (JENKINS-58751) TAG_NAME is not populated in declarative multibranch pipeline
Title: Message Title Mark Waite edited a comment on JENKINS-58751 Re: TAG_NAME is not populated in declarative multibranch pipeline Thanks for the suggestion on the documentation. I've added it to my "[Jenkins Git Use Cases|https://docs.google.com/document/d/1FNofpRVFe8WTtMpKb7exftsBOLS_qJydULlUMePswbY/edit#]" document to remind me of things that need to be documented and where they need to be documented.If you'd like to submit a pull request, the documentation is open for contributions as pull requests . The GitHub interface makes it easy to contribute even without cloning or building locally. Refer to the [when directive in the pipeline syntax|https://github.com/jenkins-infra/jenkins.io/blob/master/content/doc/book/pipeline/syntax.adoc#when]. 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.6726.1564752780231%40Atlassian.JIRA.
[JIRA] (JENKINS-58751) TAG_NAME is not populated in declarative multibranch pipeline
Title: Message Title Mark Waite commented on JENKINS-58751 Re: TAG_NAME is not populated in declarative multibranch pipeline Thanks for the suggestion on the documentation. I've added it to my "Jenkins Git Use Cases" document to remind me of things that need to be documented and where they need to be documented. If you'd like to submit a pull request, the documentation is open for contributions as pull requests. The GitHub interface makes it easy to contribute even without cloning or building locally. Refer to the when directive in the pipeline syntax. 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.6724.1564752780201%40Atlassian.JIRA.
[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 declarative multibranch pipeline
Title: Message Title
Mark Waite edited a comment on JENKINS-58751
Re: TAG_NAME is not populated in declarative multibranch pipeline
Please provide more details on the multibranch pipeline that you created. Preferably, provide step-by-step instructions that someone else can use to duplicate the problem.You said:{quote}I configured a multibranch pipeline to check out via git, discover branches, discover tags and the added clone behaviour to fetch tags.{quote}You didn't say:* What version of the git client plugin, git plugin, github branch source, bitbucket branch source, Gitea, pipeline, and other plugins you're using* Which SCM implementation you used to create the multibranch pipeline (git, GitHub branch source, Bitbucket, Gitea, something else)* What other options you configured as part of defining the multibranch pipeline* The configuration file ( {{config.xml}} ) of the multibranch pipeline that is showing the problem Assumptions I made:* {{Windows 10}} means that the Jenkins server is running on Windows 10.* Git for Windows 2.22 is being used on the Windows 10 Jenkins server. I don't see anything that hints this is somehow connected to a specific version of command line git on Windows, so I assumed the version I have installed on my Windows computer* Java 8 as provided by AdoptOpenJDK, since that is what I have installed on my Windows computer now that Oracle JDK requires a license purchase from Oracle for commercial use* Latest releases of all the relevant plugins* GitHub as the provider for the multibranch pipeline definition (not git, not Bitbucket, and not Gitea)
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
[JIRA] (JENKINS-58751) TAG_NAME is not populated in declarative multibranch pipeline
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-58751 TAG_NAME is not populated in declarative multibranch pipeline Change By: Mark Waite Summary: TAG_NAME is not populated in descriptive declarative multibranch pipeline 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.5759.1564689000159%40Atlassian.JIRA.
