-
Bug
-
Resolution: Fixed
-
Major
-
Any Jenkins
Replicated on Bitbucket Server Integration 3.2.0+
Steps to reproduce:
- Setup a new freestyle job with no branch specifier and a push trigger
- Create and push a tag to the repository (e.g. `newTag`)
Expected:
A build status is created and sent to Bitbucket with an identifier `refs/tags/newTag`
Actual:
The identifier instead is `refs/heads/refs/tags/newTag`
- causes
-
JENKINS-71770 Document "branchName" serialization compatibility between Bitbucket Server Integration 3.5.0 and 3.6.0
-
- Open
-
[JENKINS-71289] Build status URL for tag builds sent through as refs/heads/refs/tags/<tagname>
Attachment | New: css-devtools_-_Atlassian_-_152_new_items_-_Slack.jpg [ 60483 ] |
Attachment | New: css-devtools_-_Atlassian_-_152_new_items_-_Slack-1.jpg [ 60484 ] |
Labels | New: triaged |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Assignee | New: Martin Henschke [ mhenschke_atlassian ] |
Status | Original: In Progress [ 3 ] | New: In Review [ 10005 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: In Review [ 10005 ] | New: Fixed but Unreleased [ 10203 ] |
Link | New: This issue causes JENKINS-71770 [ JENKINS-71770 ] |
Update:
If it is a freestyle Jenkins project, the tags ref identifier is updated as refs/heads/refs/tags/<<tag_name>> and if it is a multi-branch pipeline project than it is updated as refs/heads/<tagname> instead of refs/tags/<tagname>.