That seems sensible to me. The issue is in the plugin, not the core. Delaying the release of the core will not help fix the plugin.
I'm not clear how a new user installing Jenkins LTS will be able to choose the 1.1.20 release of the git plugin. I had to download it separately, name it appropriately (replace .hpi with .bak), copy it into the plugins directory, then restart Jenkins. Once that was done, Jenkins core recognized there was a 1.1.20 available for downgrade. Those steps seem too complicated for the otherwise elegant and easy to administer Jenkins system. I guess the best solution is to have a new version of the Git plugin released to fix the problem... Mark Waite >________________________________ > From: Vojtech Juranek <vjura...@redhat.com> >To: jenkinsci-users@googlegroups.com >Sent: Sunday, July 22, 2012 1:21 PM >Subject: Re: Re: LTS 1.466.1 RC1 testing > >Sami, thanks for clarifying what is the root cause of this issue, it's caused >by 3b1ad20200 [1], which should fixed checking out branches containing "/" in >the branch name [2]. > >Mark, this is not a show stopper for LTS release. Git plugin is not bundled >with the Jenkins core and you can do the upgrade to 1.466.1 without upgrading >Git plugin to 1.1.21. The idea behind LTS is to provide some stable release >which includes also some basics testing of most popular plugin against this >release. I try to test with the most up-to-date plugin release, but it's not >mandatory to use the latest version. I.e. the output of the testing will be >something like the report "upgrade to 1.466.1 is fine, all latest plugin as >well except git plug. In git 1.1.21 is a regression and you should update to >1.1.20" > >In fact IIRC we never experienced such situation, that a serious regression >was find in a plugin during LTS testing. Maybe I should create separate topics >how to present this results to the community in some well-arranged way > >[1] https://github.com/jenkinsci/git- >plugin/commit/3b1ad202004ec3617f2023e147868876bea2e305 >[2] https://issues.jenkins-ci.org/browse/JENKINS-14026 > >On Sunday 22 July 2012 07:31:38 Mark Waite wrote: >> That is the issue. Thanks for the suggestion! I was confident the problem >> was in the plugin, not in jenkins core, since switching back to the old >> plugin was able to make it work again. >> >> I assume this is still a "showstopper" for the release of the 1.466.1 long >> term support version, since many, many Jenkins users depend on the Git >> plugin and this bug makes Git plugin 1.1.21 incompatible with previous >> versions and incompatible with the help which is included with the plugin. >> >> Mark Waite >> >> >________________________________ >> > >> > From: Sami Tikka <sjti...@gmail.com> >> > >> >To: "jenkinsci-users@googlegroups.com" <jenkinsci-users@googlegroups.com> >> >Cc: "jenkinsci-users@googlegroups.com" <jenkinsci-users@googlegroups.com> >> >Sent: Saturday, July 21, 2012 11:50 PM >> >Subject: Re: LTS 1.466.1 RC1 testing >> > >> >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 > > >
