[JENKINS-73502] GIT_BRANCH Variable Now Contains the Remote Name

Type: Bug
Resolution: Unresolved
Priority: Minor
Component/s: atlassian-bitbucket-server-integration-plugin
Labels:
- triaged
Environment:
atlassian-server-integration:4.0.0 git:5.2.1

Similar Issues:
Powered by SuggestiMate

Show

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

Aidan created issue - 2024-07-24 00:27

Aidan made changes - 2024-07-24 00:27

Summary

Original: GIT_BRANCH Variable Now Contains the Remote

New: GIT_BRANCH Variable Now Contains the Remote Name

Aidan made changes - 2024-07-24 00:27

Description

Original: Previously, the Bitbucket Server integration plugin use to 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 would be 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
{code:java}
stage("Case #1: Test Pod Build"){
steps{
sh "echo ${GIT_BRANCH}"
sh "echo ${env.GIT_BRANCH}"
}
} {code}

Output on 3.6.0

aidaleuc/smoketests

Output on 4.0.0

origin/aidaleuc/smoketests

New: Previously, the Bitbucket Server integration plugin use to 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 would be 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
{code:java}
stage("Case #1: Test Pod Build"){
steps{
sh "echo ${GIT_BRANCH}"
sh "echo ${env.GIT_BRANCH}"
}
} {code}
Output on 3.6.0

aidaleuc/smoketests

Output on 4.0.0

origin/aidaleuc/smoketests

Aidan made changes - 2024-07-24 00:33

Description

Original: Previously, the Bitbucket Server integration plugin use to 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 would be 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
{code:java}
stage("Case #1: Test Pod Build"){
steps{
sh "echo ${GIT_BRANCH}"
sh "echo ${env.GIT_BRANCH}"
}
} {code}
Output on 3.6.0

aidaleuc/smoketests

Output on 4.0.0

origin/aidaleuc/smoketests

New: Previously, the Bitbucket Server integration plugin use to 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 would be 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
{code:java}
stage("Print GIT_BRANCH"){
steps{
sh "echo ${GIT_BRANCH}"
}
} {code}
Output on 3.6.0

aidaleuc/smoketests

Output on 4.0.0

origin/aidaleuc/smoketests

Aidan made changes - 2024-07-24 00:34

Description

Original: Previously, the Bitbucket Server integration plugin use to 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 would be 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
{code:java}
stage("Print GIT_BRANCH"){
steps{
sh "echo ${GIT_BRANCH}"
}
} {code}
Output on 3.6.0

aidaleuc/smoketests

Output on 4.0.0

origin/aidaleuc/smoketests

New: Previously, the Bitbucket Server integration plugin use to 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 would be 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
{code:java}
stage("Print GIT_BRANCH"){
steps{
echo GIT_BRANCH
}
} {code}
Output on 3.6.0

aidaleuc/smoketests

Output on 4.0.0

origin/aidaleuc/smoketests

Aidan made changes - 2024-07-24 00:36

Description

Original: Previously, the Bitbucket Server integration plugin use to 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 would be 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
{code:java}
stage("Print GIT_BRANCH"){
steps{
echo GIT_BRANCH
}
} {code}
Output on 3.6.0

aidaleuc/smoketests

Output on 4.0.0

origin/aidaleuc/smoketests

New: Previously, the Bitbucket Server integration plugin use to 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 would be 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
{code:java}
stage("Print GIT_BRANCH"){
steps{
sh "echo ${GIT_BRANCH}"
}
} {code}
Output on 3.6.0

aidaleuc/smoketests

Output on 4.0.0

origin/aidaleuc/smoketests

Aidan made changes - 2024-07-24 00:37

Description

Original: Previously, the Bitbucket Server integration plugin use to 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 would be 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
{code:java}
stage("Print GIT_BRANCH"){
steps{
sh "echo ${GIT_BRANCH}"
}
} {code}
Output on 3.6.0

aidaleuc/smoketests

Output on 4.0.0

origin/aidaleuc/smoketests

New: Previously, the Bitbucket Server integration plugin use to 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 would be 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
{code:java}
stage("Print GIT_BRANCH"){
steps{
echo env.GIT_BRANCH
}
} {code}
Output on 3.6.0

aidaleuc/smoketests

Output on 4.0.0

origin/aidaleuc/smoketests

Aidan made changes - 2024-07-24 00:41

Description

Original: Previously, the Bitbucket Server integration plugin use to 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 would be 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
{code:java}
stage("Print GIT_BRANCH"){
steps{
echo env.GIT_BRANCH
}
} {code}
Output on 3.6.0

aidaleuc/smoketests

Output on 4.0.0

origin/aidaleuc/smoketests

New: 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 would be 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
{code:java}
stage("Print GIT_BRANCH"){
steps{
echo env.GIT_BRANCH
}
} {code}
Output on 3.6.0

aidaleuc/smoketests

Output on 4.0.0

origin/aidaleuc/smoketests

Aidan made changes - 2024-07-24 00:41

Description

Original: 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 would be 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
{code:java}
stage("Print GIT_BRANCH"){
steps{
echo env.GIT_BRANCH
}
} {code}
Output on 3.6.0

aidaleuc/smoketests

Output on 4.0.0

origin/aidaleuc/smoketests

New: 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
{code:java}
stage("Print GIT_BRANCH"){
steps{
echo env.GIT_BRANCH
}
} {code}
Output on 3.6.0

aidaleuc/smoketests

Output on 4.0.0

origin/aidaleuc/smoketests

Sunny made changes - 2024-08-01 04:45

Labels

New: triaged

Assignee:: Unassigned

Reporter:: Aidan

Votes:: 2 Vote for this issue

Watchers:: 3 Start watching this issue

Created:: 2024-07-24 00:27

Updated:: 2024-08-01 04:45

Jenkins

Details

Description

Attachments

Activity

People

Dates