[JIRA] (JENKINS-59206) Environment variables tag name and branch name set incorrectly

[mark.earl.wa...@gmail.com (JIRA)]

Title: Message Title

Mark Waite edited a comment on JENKINS-59206   Re: Environment variables tag name and branch name set incorrectly I disagree.  A tag does not reliably have an association to a branch.   A tag is a "a pointer to a specific commit".  It identifies a specific commit by providing a simplified name to describe that commit. A branch is a " lightweight movable pointer". Depending on the state of the repository, a tag may be on no branch, one branch, or many branches.  Attempting to assign a branch name which is not the name of the tag is hard or impossible to do reliably. Output from the command {{git log --graph --pretty=oneline --abbrev-commit --decorate}}: {noformat} * dd46d51 (HEAD -> master) More information added * f6db255 Add another date * dacdad4 (tag: v2.0) Another new change * c4825db Add comment about v1.1 | * ec23f88 (branch-1.x) Another README change | * 8c5c32a New change on branch-1.x | | * a6a83ee (tag: orphan-v1.1) Orphan change, no branch | |/ | * 1df4892 A newer change on branch-1.x | * 3990059 (tag: v1.0) A change on branch-1.x |/ * a693bf7 Add comment about tag * 183db1f Add README {noformat} In that case, the tag {{orphan-1.1}} is not directly associated with any branch, while the tag {{v1.0}} might be associated with {{branch-1x}}.  However, if branch-1.x is merged into master, then the tag {{v1.0}} might be associated with both {{branch-1.x}} and {{master}}. 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.201655.1567527731000.5980.1567532880309%40Atlassian.JIRA.