-
Bug
-
Resolution: Fixed
-
Major
-
None
-
git-plugin 2.3.5
This is a follow-up to JENKINS-14276. I'm creating this to better track the issues I fixed in my original pull-request [1], which I will update accordingly.
To reproduce:
- A parametrized build with parameter BRANCH_TO_BUILD, with default value "branch1"
- Git SCM with branch specifier "${BRANCH_TO_BUILD}"
- SCM polling enabled
- Previous manual job launch with BRANCH_TO_BUILD=branch2
Expected:
- When polling, BRANCH_TO_BUILD is set to branch1 (default value), so only updates to branch1 trigger a build.
Actual:
- When polling, BRANCH_TO_BUILD is set to branch2 (value from last execution).
- is duplicated by
-
JENKINS-27327 When specifying the branch to poll as part of a parameterized build, git-plugin uses last polled branch instead
-
- Closed
-
[JENKINS-27349] Git SCM-polling uses wrong parameter values for a parametrized branchspec
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
Link |
New:
This issue is duplicated by |
Workflow | Original: JNJira [ 161554 ] | New: JNJira + In-Review [ 208517 ] |