-
Bug
-
Resolution: Won't Fix
-
Major
-
Jenkins 2.332.3 and Jenkins 2.414.3
git plugin version: 5.2.1 and 4.11.1
When I ran a shell script through pipeline job today, I found that the Git_Branch parameter value I got from the bash script was different from the Git_Branch value I passed in when I triggered the job.
After analysis and debugging, I found that the git plugin tampered with the value of the job parameter Git_Branch. And I found that freestyle job had similar issue.
The phenomenon is as follows:
When I use b1234567 to trigger the pipeline job, the value the Git_Branch shell script gets is the branch information used by the git plug-in.
When I trigger freestyle job in the same way, the Git_Branch value is overwritten when the git plug-in is used.
The Git_Branch value is correctly get when the git plug-in is not used
[JENKINS-72366] The job param Git_Branch is overwritten by git plugin when build
Summary | Original: The Git_Branch variable is overwritten when the job is built | New: The Git_Branch variable is overwritten git plugin when build |
Summary | Original: The Git_Branch variable is overwritten git plugin when build | New: The variable Git_Branch is overwritten git plugin when build |
Summary | Original: The variable Git_Branch is overwritten git plugin when build | New: The variable Git_Branch is overwritten by git plugin when build |
Summary | Original: The variable Git_Branch is overwritten by git plugin when build | New: The job param Git_Branch is overwritten by git plugin when build |
Resolution | New: Won't Fix [ 2 ] | |
Status | Original: Open [ 1 ] | New: Closed [ 6 ] |