-
Bug
-
Resolution: Fixed
-
Critical
-
Windows Server 2008 R2, Jenkins 1.454, Git Plugin 1.1.16, Git version 1.7.9-preview20120201
It appears a bug has been introduced in Git plugin 1.1.16:
If I set the branch specifier in the "Branches to Build" section, I always get the following error.
ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.
The only way I found to resolve this is to get rid of the branch specifier and replace it with **. However, I only want to build a specific branch in our Git repo, so in the meantime I've rolled back to 1.1.15 where this functionality is working just fine.
- duplicates
-
-
- Closed
-
- is related to
-
-
- Closed
-
[JENKINS-13051] Setting branch name prevents branch from building
Steve Kluth
added a comment - +1: Server 2008 R2, x64, Git-1.7.9-preview20120201, Jenkins 1.458. Rollback to 1.1.15 fixed for me as well.
Steve Kluth
added a comment - +1: Server 2008 R2, x64, Git-1.7.9-preview20120201, Jenkins 1.458. Rollback to 1.1.15 fixed for me as well. 
Rob Schoeing
added a comment - This is definite show-stopper. Rolling back to 1.1.15 fixes the problem for me as well.
I'm not familiar with the codebase, but browsing through the diffs for 1.1.16, this particular change pops out at me as a possible culprit:
https://github.com/jenkinsci/git-plugin/compare/git-1.1.15...git-1.1.16#diff-1
Rob Schoeing
added a comment - This is definite show-stopper. Rolling back to 1.1.15 fixes the problem for me as well.
I'm not familiar with the codebase, but browsing through the diffs for 1.1.16, this particular change pops out at me as a possible culprit:
https://github.com/jenkinsci/git-plugin/compare/git-1.1.15...git-1.1.16#diff-1 
Milutin Jovanovic
added a comment - A workaroung that works for me is to spacify two branches to build, first master and then the one I actually want to build. Interestingly, only one branch is built this way, the second one.
Milutin Jovanovic
added a comment - A workaroung that works for me is to spacify two branches to build, first master and then the one I actually want to build. Interestingly, only one branch is built this way, the second one. I was able to work around this issue with the latest plugin (1.1.17) by using the branch name as **/master. However, this only works if you are only working with one repository. Setting the branch name as origin/master fails, even though the Git polling log calls the branch origin/master.
Adam Westhusing
added a comment - - edited I was able to work around this issue with the latest plugin (1.1.17) by using the branch name as **/master. However, this only works if you are only working with one repository. Setting the branch name as origin/master fails, even though the Git polling log calls the branch origin/master. Rolling back to 1.1.15 from 1.1.18 fixes the problem for me as well (on windows Server 2008 x64 SP2).
I am using Jenkins 1.463
Eric Fleischman
added a comment - +1 repro, and same fix mentioned above worked for me. Latest Jenkins, Git Plugin, Win2k8 R2, Git ver 1.7.9-preview...
Eric Fleischman
added a comment - +1 repro, and same fix mentioned above worked for me. Latest Jenkins, Git Plugin, Win2k8 R2, Git ver 1.7.9-preview... Eric Fleischman
added a comment - +1...same bug/repro/workaround worked for me. I am seeing more reports of this in the wild fwiw.
Eric Fleischman
added a comment - +1...same bug/repro/workaround worked for me. I am seeing more reports of this in the wild fwiw. 
Yury Zaytsev
added a comment - Still broken in 1.1.19. Aie! 
I see this too, with git 1.7.0.4 (on Cygwin 1.7.5), git plugin 1.1.16, Jenkins 1.437. I updated the git plugin yesterday and lots of jobs are now failing with this error. It's pretty much a show-stopper for me, so will roll back to 1.1.15 in the meantime.