More details in case it helps. If I install Jenkins 1.466.1 and the latest Git plugin, 1.1.21, and define a job using the command line interface create-job command and a config.xml, it fails to clone with messages:
Fetching upstream changes from git://markwaite2.markwaite.net/git/WorkManager.git ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job. If I install Jenkins 1.466.1 and If I copy the git.hpi file for Git plugin version 1.1.20 into the plugins directory as git.bak, restart Jenkins, and downgrade the plugin to 1.1.20, then the same jobs that were failing to find a revision are now able to find that revision and run the job to completion. The only change I recognize between the failure case and the success case is the version of the Git plugin. Any suggestions of other steps I should take to further isolate the problem? Mark Waite >________________________________ > From: Mark Waite <markwa...@yahoo.com> >To: "jenkinsci-users@googlegroups.com" <jenkinsci-users@googlegroups.com> >Sent: Friday, July 20, 2012 9:21 PM >Subject: Re: LTS 1.466.1 RC1 testing > > >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 >> >> >> > >
