-
Bug
-
Resolution: Unresolved
-
Minor
-
atlassian-server-integration:4.0.0 git:5.2.1
Previously, the Bitbucket Server integration plugin set the GIT_BRANCH environment variable equal to the local branch name checked out by Jenkins. In versions of the plugin < 3.6.0 a multibranch pipeline's job named example/example-branch would have a GIT_BRANCH variable set to example-branch. After upgrading to 4.0.0 of the plugins, that same variable would be origin/example-branch. This is breaking a lot of our Jenkinsfiles that depend on the previous behavior.
Example code
stage("Print GIT_BRANCH"){
steps{
echo env.GIT_BRANCH
}
}
Output on 3.6.0
aidaleuc/smoketests
Output on 4.0.0
origin/aidaleuc/smoketests
Hi Aidan, thanks for the report. We've confirmed it, this is a case of us breaking API without realising as part of the 4.0 release and is a valid issue.
We need to investigate this further so we can provide better instruction on how to move forward but so far I think we agree this change was unintentional and the "origin/" should be stripped from the response in a future bugfix release- this will be confirmed on the ticket when it is picked up.
Thanks,
Martin