Re: Re: Re: LTS 1.466.1 RC1 testing

2012-07-23 Thread Vojtech Juranek
> 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 > r

Re: Re: LTS 1.466.1 RC1 testing

2012-07-22 Thread Mark Waite
s the best solution is to have a new version of the Git plugin released to fix the problem... Mark Waite > > From: Vojtech Juranek >To: jenkinsci-users@googlegroups.com >Sent: Sunday, July 22, 2012 1:21 PM >Subject: Re: Re: LTS 1.466.1 RC1 testing

Re: Re: LTS 1.466.1 RC1 testing

2012-07-22 Thread Vojtech Juranek
with the help which is included with the plugin. > > Mark Waite > > > > > > > From: Sami Tikka > > > >To: "jenkinsci-users@googlegroups.com" > >Cc: "jenkinsci-users@googlegroups.com" > >Sent: Saturday, July 21, 2012 11:50 PM > >Subje

Re: LTS 1.466.1 RC1 testing

2012-07-22 Thread Mark Waite
i-users@googlegroups.com" >Cc: "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

Re: LTS 1.466.1 RC1 testing

2012-07-21 Thread Sami Tikka
e: >> I used the script console at http://localhost:8080/script to run the >> command Functions.isWindows() and it reports Result: false >>> >>> >>> From: Vojtech Juranek >>> >>> To: jenkinsci-users@goog

Re: Re: Re: LTS 1.466.1 RC1 testing

2012-07-21 Thread Vojtech Juranek
rday, 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 co

Re: Re: LTS 1.466.1 RC1 testing

2012-07-21 Thread Mark Waite
I used the script console at http://localhost:8080/script to run the command Functions.isWindows() and it reports Result: false > > From: Vojtech Juranek >To: jenkinsci-users@googlegroups.com >Sent: Saturday, July 21, 2012 3:00 PM >Subject: Re:

Re: Re: LTS 1.466.1 RC1 testing

2012-07-21 Thread Mark Waite
rs@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

Re: Re: LTS 1.466.1 RC1 testing

2012-07-21 Thread Mark Waite
> From: Vojtech Juranek >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

Re: Re: LTS 1.466.1 RC1 testing

2012-07-21 Thread Vojtech Juranek
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 machin

Re: LTS 1.466.1 RC1 testing

2012-07-20 Thread Mark Waite
e the problem? Mark Waite > > From: Mark Waite >To: "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 checko

Re: LTS 1.466.1 RC1 testing

2012-07-20 Thread Mark Waite
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