|
Adam Westhusing created JENKINS-13051:
----------------------------------------- Summary: 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 Reporter: Adam Westhusing Assignee: Nicolas De Loof Priority: Critical 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 |
|
[ https://issues.jenkins-ci.org/browse/JENKINS-13051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Westhusing updated JENKINS-13051: -------------------------------------- Environment: Windows Server 2008 R2, Jenkins 1.454, Git Plugin 1.1.16 (was: Windows Server 2008 R2) > 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 > 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 |
|
In reply to this post by JIRA noreply@jenkins-ci.org
[ https://issues.jenkins-ci.org/browse/JENKINS-13051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Westhusing updated JENKINS-13051: -------------------------------------- Environment: Windows Server 2008 R2, Jenkins 1.454, Git Plugin 1.1.16, Git version 1.7.9-preview20120201 (was: Windows Server 2008 R2, Jenkins 1.454, Git Plugin 1.1.16) > 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 |
|
In reply to this post by JIRA noreply@jenkins-ci.org
[ https://issues.jenkins-ci.org/browse/JENKINS-13051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160300#comment-160300 ] Bevan Watkiss commented on JENKINS-13051: ----------------------------------------- I have noticed this too. It seems to actually be replacing the variable with the job name. > 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 |
|
In reply to this post by JIRA noreply@jenkins-ci.org
[ https://issues.jenkins-ci.org/browse/JENKINS-13051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161100#comment-161100 ] Dave Hansen commented on JENKINS-13051: --------------------------------------- Confirmed on similar Server 20008 RC environment with Git version 1.7.8-preview20111206 on same environment and Jenkins 1.457. > 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 |
|
In reply to this post by JIRA noreply@jenkins-ci.org
[ https://issues.jenkins-ci.org/browse/JENKINS-13051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161113#comment-161113 ] dantliff commented on JENKINS-13051: ------------------------------------ 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. > 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 |
|
In reply to this post by JIRA noreply@jenkins-ci.org
[ https://issues.jenkins-ci.org/browse/JENKINS-13051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161193#comment-161193 ] Steve Kluth commented on JENKINS-13051: --------------------------------------- +1: Server 2008 R2, x64, Git-1.7.9-preview20120201, Jenkins 1.458. Rollback to 1.1.15 fixed for me as well. > 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 |
|
In reply to this post by JIRA noreply@jenkins-ci.org
[ 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 |
|
In reply to this post by JIRA noreply@jenkins-ci.org
[ https://issues.jenkins-ci.org/browse/JENKINS-13051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161793#comment-161793 ] Milutin Jovanovic commented on JENKINS-13051: --------------------------------------------- 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. > 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 |
|
In reply to this post by JIRA noreply@jenkins-ci.org
[ https://issues.jenkins-ci.org/browse/JENKINS-13051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161823#comment-161823 ] Adam Westhusing commented on JENKINS-13051: ------------------------------------------- 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 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 |
|
In reply to this post by JIRA noreply@jenkins-ci.org
[ https://issues.jenkins-ci.org/browse/JENKINS-13051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161823#comment-161823 ] Adam Westhusing edited comment on JENKINS-13051 at 4/20/12 6:39 PM: -------------------------------------------------------------------- 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. was (Author: westhusing): 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 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 |
|
In reply to this post by JIRA noreply@jenkins-ci.org
[ https://issues.jenkins-ci.org/browse/JENKINS-13051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162606#comment-162606 ] chanti vlad commented on JENKINS-13051: --------------------------------------- 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 > 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 |
|
In reply to this post by JIRA noreply@jenkins-ci.org
|
|||||||||||
|
In reply to this post by JIRA noreply@jenkins-ci.org
|
|||||||||||
|
In reply to this post by JIRA noreply@jenkins-ci.org
|
|||||||||||
|
In reply to this post by JIRA noreply@jenkins-ci.org
|
|||||||||||||||||||
| Powered by Nabble | Edit this page |

+1 repro, and same fix mentioned above worked for me. Latest Jenkins, Git Plugin, Win2k8 R2, Git ver 1.7.9-preview...