It could be https://issues.jenkins-ci.org/browse/JENKINS-14480, probably nothing wrong with Jenkins. Mark, could you check if you have repository/branchname in the "Branch to build" setting?
-- Sami Vojtech Juranek <vjura...@redhat.com> kirjoitti 22.7.2012 kello 3.37: > Thanks for verifying. So now I really have no idea where the problem could > be:-( > And yes, I also tested with 1.466.1-SNAPSHOT (rc-07/12/2012 03:57 GMT- > kohsuke), namely rpm package downloaded from http://pkg.jenkins-ci.org/redhat- > stable-rc/ > > > On Saturday 21 July 2012 15:04:17 Mark Waite wrote: >> I used the script console at http://localhost:8080/script to run the >> command Functions.isWindows() and it reports Result: false >>> ________________________________ >>> >>> From: Vojtech Juranek <vjura...@redhat.com> >>> >>> To: jenkinsci-users@googlegroups.com >>> Sent: Saturday, July 21, 2012 3:00 PM >>> Subject: Re: Re: LTS 1.466.1 RC1 testing >>> >>> Hi Mark, >>> thanks for spotting it! >>> >>> I tested 1.466.1 RC1 with git plugin 1.1.21 and everything works fine for >>> me. You probably suffer from JENKINS-13007 [1], the last comment under >>> this issue also states that this issue start to appear on linux since >>> 1.1.21. It obviously appear only on some machines, but I have currently no >>> idea what triggers this problem. >>> >>> In 1.1.21 was one commit related to this issue [2], but it should affect >>> only windows machines... Just for sure, could you please go to >>> $JENKINS_HOME/script and run following command: >>> Functions.isWindows() >>> if Jenkins for some strange reason thinks that it runs on windows? >>> >>> Thanks >>> Vojta >>> >>> [1] https://issues.jenkins-ci.org/browse/JENKINS-13007 >>> [2] https://github.com/jenkinsci/git- >>> plugin/commit/85afc7b0e64dd18c2807373880d1a8e2824fffbc >>> >>> On Friday 20 July 2012 20:21:58 Mark Waite wrote: >>>> I installed the release candidate and cannot seem to checkout with the >>>> latest release of the Git plugin. Has anyone else successfully used Git >>>> plugin 1.1.21 with a new installation of Jenkins 1.466.1 RC1? >>>> >>>> I had seen the same problem with an existing installation and rolled back >>>> to 1.1.20 on that existing installation. Unfortunately, it is not that >>>> simple with a new installation. >>>> >>>> Mark Waite >>>> >>>>> ________________________________ >>>>> >>>>> From: Vojtech Juranek <vjura...@redhat.com> >>>>> >>>>> To: jenkinsci-...@googlegroups.com; jenkinsci-users@googlegroups.com >>>>> Sent: Friday, July 20, 2012 5:04 PM >>>>> Subject: LTS 1.466.1 RC1 testing >>>>> >>>>> Hi, >>>>> LTS 1.466.1 RC1 is now available for download [1], thus we can start >>>>> testing. As usual, I would like to ask for your help. If you stage RC in >>>>> you stage environment or just download RC and try to run it, please drop >>>>> a >>>>> note on wiki page [2], shortly describe what you tested, where it was >>>>> done >>>>> (OS, JDK version) and the result. >>>>> >>>>> Feel free to add new tests or repeating test which was already done by >>>>> someone else in different env. - it is also very useful as some bug can >>>>> appear only on e.g. one OS but not on other etc. >>>>> >>>>> Any test is very helpful, especially in case of new major LTS RC. >>>>> >>>>> Thanks in advance >>>>> Vojta >>>>> >>>>> [1] http://mirrors.jenkins-ci.org/ >>>>> [2] https://wiki.jenkins-ci.org/display/JENKINS/LTS+1.466.x+RC+Testing