-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
Production
Git plugin ver: 2.4.4
In jenkins job we configure Git plugin ->
Branches to build/Branch specifier: origin/ready/**
Developer pushes code to central git repository, which Jenkins check into 2 branches:
git push origin bugfix:sergey/bugfix
git push origin bugfix:ready/bugfix
When Jenkins job kicks in, it provides this output:
14:01:36 > git branch -a -v --no-abbrev --contains 24ef859065480d5ac965652cfce8a0dd959fd082 # timeout=10
14:01:36 Checking out Revision 24ef859065480d5ac965652cfce8a0dd959fd082 (origin/sergey/bugfix, origin/ready/bugfix)
..
..
14:01:36 HOME=/var/lib/jenkins
14:01:36 GIT_BRANCH=origin/sergey/bugfix
14:01:36 EXECUTOR_NUMBER=1
As you can see GIT_BRANCH got set to "origin/sergey/bugfix"
and this is wrong because we asked for branch to match origin/ready/**
This causes problems in our build process
- is related to
-
JENKINS-35162 git plugin does not respect refspec
-
- Closed
-
Thanks Mark for the explanation. Could you please elaborate on the using custom refspecs? I eventually have to extend my Jenkins job for the following Branch specifiers:
Branch specifier 1 - origin/develop
Branch Specifier 2 - origin/release**
(But would like to ignore these set of branches - origin/feature** and origin/bugfix**)
Would that require specifying multiple refspecs? Would you have a screenshot to share?