[
https://issues.jenkins-ci.org/browse/JENKINS-13051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161442#comment-161442
]
Rob Schoeing commented on JENKINS-13051:
----------------------------------------
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
> Setting branch name prevents branch from building
> -------------------------------------------------
>
> Key: JENKINS-13051
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13051
> Project: Jenkins
> Issue Type: Bug
> Components: git
> Environment: Windows Server 2008 R2, Jenkins 1.454, Git Plugin
> 1.1.16, Git version 1.7.9-preview20120201
> Reporter: Adam Westhusing
> Assignee: Nicolas De Loof
> Priority: Critical
> Labels: git, plugin, windows
>
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
