Re: Is there a chance to get Subversion 1.8.x running with jenkins?

2014-01-02 Thread Mike Konikoff
There is an open issue for this here 
https://issues.jenkins-ci.org/browse/JENKINS-18935

On Wednesday, July 31, 2013 9:33:55 AM UTC-4, Kevin Fleming wrote:

 Are you saying that SvnKit in Jenkins can't talk to a Subversion 1.8 
 server? That would be quite surprising, so I suspect that you are having 
 problems because you are sharing a Subversion checkout (working copy) 
 between Jenkins jobs and other uses, and they are using different versions 
 of Subversion.

 If so, don't do that! The Jenkins workspace should be used only by Jenkins.

 - Original Message -
 From: jenkins...@googlegroups.com javascript:
 To: jenkins...@googlegroups.com javascript:
 At: Jul 30 2013 17:03:54

 Hi!

 I made a big mistake. I changed our subversion to the newest version. 
 Everything works fine. All our IDEs and tools are able to handle it, but 
 not Jenkins.

 As I understood, Jenkins uses SVNKIT. There is an alpha version of SVNKIT 
 which supports the subversion 1.8.x format.

 Is there a chance for me, to get this alpha version running in our Jenkins 
 installation?

 Thanks,
 Christian.

 -- 
 You received this message because you are subscribed to the Google Groups 
 Jenkins Users group.
 To unsubscribe from this group and stop receiving emails from it, send an 
 email to jenkinsci-use...@googlegroups.com javascript:.
 For more options, visit https://groups.google.com/groups/opt_out.
  
  



-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


Re: Is there a chance to get Subversion 1.8.x running with jenkins?

2013-10-31 Thread Matthias
For me it worked to delete all SVN checkouts that where checked out with 
SVN 1.8x and let Jenkins download the projects from the SVN Server.

greetings
Matthias



Am Freitag, 2. August 2013 08:47:55 UTC+2 schrieb cjs1976:

 Hi!

 I made a mistake: I updated our lokal svn-server to the newest version (= 
 Subversion 1.8.x). The update worked fine (no errors), and while the update 
 process all files were automatically changed to the new format of 
 Subversion 1.8.x.

 If we do a checkout (or whatever) from our svn-server to our local IDEs, 
 everything workes fine.

 Only Jenkins (also the newst version) seems to have a problem with the new 
 svn format. I found out, that the SVNKit version used in the actual Jenkins 
 version doesn't support Subversion 1.8.x. There is an alpaha version of the 
 newxt SVNKit version wthich would support the new format, but not all new 
 Subversion 1.8.x features.

 But I don't know how I can manually change to the alpha version of the 
 SVNKit.

 Here a part of the error messages from Jenkins:

 ***

 [ERROR] Provider message:

 [ERROR] The svn command failed.

 [ERROR] Command output:

 [ERROR] svn: E155036: Please see the 'svn upgrade' command

 svn: E155036: The working copy at '
 http://my.server.org/jenkins/job/mysoftware/org.company.my$mysoftware/ws/'http://glassfish.software-agentur.com:8080/jenkins/job/saAVA/biz.soag.saava$saAVA/ws/'
 

 is too old (format 29) to work with client version '1.8.0 (r1490375)' 
 (expects format 31). You need to upgrade the working copy first.
 ***

 Any idea?

 Greetings,
 Christian.


 Am Mittwoch, 31. Juli 2013 15:33:55 UTC+2 schrieb Kevin Fleming:

 Are you saying that SvnKit in Jenkins can't talk to a Subversion 1.8 
 server? That would be quite surprising, so I suspect that you are having 
 problems because you are sharing a Subversion checkout (working copy) 
 between Jenkins jobs and other uses, and they are using different versions 
 of Subversion.

 If so, don't do that! The Jenkins workspace should be used only by 
 Jenkins.

 - Original Message -
 From: jenkins...@googlegroups.com
 To: jenkins...@googlegroups.com
 At: Jul 30 2013 17:03:54

 Hi!

 I made a big mistake. I changed our subversion to the newest version. 
 Everything works fine. All our IDEs and tools are able to handle it, but 
 not Jenkins.

 As I understood, Jenkins uses SVNKIT. There is an alpha version of SVNKIT 
 which supports the subversion 1.8.x format.

 Is there a chance for me, to get this alpha version running in our 
 Jenkins installation?

 Thanks,
 Christian.

 -- 
 You received this message because you are subscribed to the Google Groups 
 Jenkins Users group.
 To unsubscribe from this group and stop receiving emails from it, send an 
 email to jenkinsci-use...@googlegroups.com.
 For more options, visit https://groups.google.com/groups/opt_out.
  
  



-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


Re: Is there a chance to get Subversion 1.8.x running with jenkins?

2013-08-02 Thread cjs1976
Hi!

I made a mistake: I updated our lokal svn-server to the newest version (= 
Subversion 1.8.x). The update worked fine (no errors), and while the update 
process all files were automatically changed to the new format of 
Subversion 1.8.x.

If we do a checkout (or whatever) from our svn-server to our local IDEs, 
everything workes fine.

Only Jenkins (also the newst version) seems to have a problem with the new 
svn format. I found out, that the SVNKit version used in the actual Jenkins 
version doesn't support Subversion 1.8.x. There is an alpaha version of the 
newxt SVNKit version wthich would support the new format, but not all new 
Subversion 1.8.x features.

But I don't know how I can manually change to the alpha version of the 
SVNKit.

Here a part of the error messages from Jenkins:

***

[ERROR] Provider message:

[ERROR] The svn command failed.

[ERROR] Command output:

[ERROR] svn: E155036: Please see the 'svn upgrade' command

svn: E155036: The working copy at '
http://my.server.org/jenkins/job/mysoftware/org.company.my$mysoftware/ws/'http://glassfish.software-agentur.com:8080/jenkins/job/saAVA/biz.soag.saava$saAVA/ws/'


is too old (format 29) to work with client version '1.8.0 (r1490375)' 
(expects format 31). You need to upgrade the working copy first.
***

Any idea?

Greetings,
Christian.


Am Mittwoch, 31. Juli 2013 15:33:55 UTC+2 schrieb Kevin Fleming:

 Are you saying that SvnKit in Jenkins can't talk to a Subversion 1.8 
 server? That would be quite surprising, so I suspect that you are having 
 problems because you are sharing a Subversion checkout (working copy) 
 between Jenkins jobs and other uses, and they are using different versions 
 of Subversion.

 If so, don't do that! The Jenkins workspace should be used only by Jenkins.

 - Original Message -
 From: jenkins...@googlegroups.com javascript:
 To: jenkins...@googlegroups.com javascript:
 At: Jul 30 2013 17:03:54

 Hi!

 I made a big mistake. I changed our subversion to the newest version. 
 Everything works fine. All our IDEs and tools are able to handle it, but 
 not Jenkins.

 As I understood, Jenkins uses SVNKIT. There is an alpha version of SVNKIT 
 which supports the subversion 1.8.x format.

 Is there a chance for me, to get this alpha version running in our Jenkins 
 installation?

 Thanks,
 Christian.

 -- 
 You received this message because you are subscribed to the Google Groups 
 Jenkins Users group.
 To unsubscribe from this group and stop receiving emails from it, send an 
 email to jenkinsci-use...@googlegroups.com javascript:.
 For more options, visit https://groups.google.com/groups/opt_out.
  
  



-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.




Re:Is there a chance to get Subversion 1.8.x running with jenkins?

2013-07-31 Thread Kevin Fleming (BLOOMBERG/ 731 LEXIN)
Are you saying that SvnKit in Jenkins can't talk to a Subversion 1.8 server? 
That would be quite surprising, so I suspect that you are having problems 
because you are sharing a Subversion checkout (working copy) between Jenkins 
jobs and other uses, and they are using different versions of Subversion.

If so, don't do that! The Jenkins workspace should be used only by Jenkins.

- Original Message -
From: jenkinsci-users@googlegroups.com
To: jenkinsci-users@googlegroups.com
At: Jul 30 2013 17:03:54

Hi!

I made a big mistake. I changed our subversion to the newest version. 
Everything works fine. All our IDEs and tools are able to handle it, but not 
Jenkins.

As I understood, Jenkins uses SVNKIT. There is an alpha version of SVNKIT which 
supports the subversion 1.8.x format.

Is there a chance for me, to get this alpha version running in our Jenkins 
installation?

Thanks,
Christian.-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.




Is there a chance to get Subversion 1.8.x running with jenkins?

2013-07-30 Thread cjs1976
Hi!

I made a big mistake. I changed our subversion to the newest version. 
Everything works fine. All our IDEs and tools are able to handle it, but 
not Jenkins.

As I understood, Jenkins uses SVNKIT. There is an alpha version of SVNKIT 
which supports the subversion 1.8.x format.

Is there a chance for me, to get this alpha version running in our Jenkins 
installation?

Thanks,
Christian.

-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.