[JIRA] Created: (JENKINS-11381) Subversion Plugin does not support Subversion 1.7
soundworker@java.net (JIRA)
-------------------------------------------------
Key: JENKINS-11381
URL: https://issues.jenkins-ci.org/browse/JENKINS-11381
Project: Jenkins
Issue Type: Improvement
Components: subversion
Reporter: soundworker
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
gavinb@thespidernet.com (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=154078#comment-154078 ]
Gavin Baumanis commented on JENKINS-11381:
------------------------------------------
Hi Everyone,
I have (unfortunately) no java skills to assist with a solution.
But please let me add my +1 to the requirement to support SVN 1.7
We have recently upgraded SVN to 1.7
(It solves a few major issues we had with 1.6)
And subsequently cannot use Jenkins for checking out / updating our code.
We are able to do this via ANT, but it is slightly painful.
Gavin.
> Subversion Plugin does not support Subversion 1.7
> -------------------------------------------------
>
> Key: JENKINS-11381
> URL: https://issues.jenkins-ci.org/browse/JENKINS-11381
> Project: Jenkins
> Issue Type: Improvement
> Components: subversion
> Reporter: soundworker
> Priority: Minor
john.manko@gmail.com (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=154109#comment-154109 ]
John Manko commented on JENKINS-11381:
--------------------------------------
This is a critical bug. I just updated my subversion installation, and it broke Jenkins. I can't downgrade svn at this time.
> Subversion Plugin does not support Subversion 1.7
> -------------------------------------------------
>
> Key: JENKINS-11381
> URL: https://issues.jenkins-ci.org/browse/JENKINS-11381
> Project: Jenkins
> Issue Type: Improvement
> Components: subversion
> Reporter: soundworker
> Priority: Minor
john.manko@gmail.com (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John Manko updated JENKINS-11381:
---------------------------------
Priority: Critical (was: Minor)
> Subversion Plugin does not support Subversion 1.7
> -------------------------------------------------
>
> Key: JENKINS-11381
> URL: https://issues.jenkins-ci.org/browse/JENKINS-11381
> Project: Jenkins
> Issue Type: Improvement
> Components: subversion
> Reporter: soundworker
> Priority: Critical
kutzi@gmx.de (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=154110#comment-154110 ]
kutzi commented on JENKINS-11381:
---------------------------------
Jenkins uses SVNKit internally for subversion support. Until SVNKit doesn't support 1.7 - announced for end of November http://svnkit.com/download.php - I'm afraid there isn't much we can do about it.
> Subversion Plugin does not support Subversion 1.7
> -------------------------------------------------
>
> Key: JENKINS-11381
> URL: https://issues.jenkins-ci.org/browse/JENKINS-11381
> Project: Jenkins
> Issue Type: Improvement
> Components: subversion
> Reporter: soundworker
> Priority: Critical
zacharysyoung@gmail.com (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=154481#comment-154481 ]
Zachary Young edited comment on JENKINS-11381 at 10/21/11 11:05 PM:
--------------------------------------------------------------------
Thank you for the update @kutzi.
was (Author: zacharysyoung):
Thank you for the update kutzi.
> Subversion Plugin does not support Subversion 1.7
> -------------------------------------------------
>
> Key: JENKINS-11381
> URL: https://issues.jenkins-ci.org/browse/JENKINS-11381
> Project: Jenkins
> Issue Type: Improvement
> Components: subversion
> Reporter: soundworker
> Priority: Critical
zacharysyoung@gmail.com (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=154481#comment-154481 ]
Zachary Young commented on JENKINS-11381:
-----------------------------------------
Thank you for the update kutzi.
> Subversion Plugin does not support Subversion 1.7
> -------------------------------------------------
>
> Key: JENKINS-11381
> URL: https://issues.jenkins-ci.org/browse/JENKINS-11381
> Project: Jenkins
> Issue Type: Improvement
> Components: subversion
> Reporter: soundworker
> Priority: Critical
zacharysyoung@gmail.com (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=154481#comment-154481 ]
Zachary Young edited comment on JENKINS-11381 at 10/21/11 11:06 PM:
--------------------------------------------------------------------
Thank you for the update [~kutzi].
was (Author: zacharysyoung):
Thank you for the update @kutzi.
> Subversion Plugin does not support Subversion 1.7
> -------------------------------------------------
>
> Key: JENKINS-11381
> URL: https://issues.jenkins-ci.org/browse/JENKINS-11381
> Project: Jenkins
> Issue Type: Improvement
> Components: subversion
> Reporter: soundworker
> Priority: Critical
jovanovic.milutin@gmail.com (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=154903#comment-154903 ]
Milutin Jovanovic commented on JENKINS-11381:
---------------------------------------------
Does anyone know a workaround, even temporary/unstable one? I tried finding the unstable svnkit jars, but could not find them. Before I spend the time figuring out how to build it, I am curious, would simply replacing the Jenkins svnkit jars be a possible workaround?
Is there a possibility of using JavaHL with Jenkins svn plugin?
P.S. Thanks for your hard work. This is my first Jenkins issue in two years of usage.
> Subversion Plugin does not support Subversion 1.7
> -------------------------------------------------
>
> Key: JENKINS-11381
> URL: https://issues.jenkins-ci.org/browse/JENKINS-11381
> Project: Jenkins
> Issue Type: Improvement
> Components: subversion
> Reporter: soundworker
> Priority: Critical
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
jovanovic.milutin@gmail.com (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=154912#comment-154912 ]
Milutin Jovanovic commented on JENKINS-11381:
---------------------------------------------
BTW, I attempted simple jar substitution with trunk of svnkit, and that did not work. Bunch of missing class def exception.
> Subversion Plugin does not support Subversion 1.7
> -------------------------------------------------
>
> Key: JENKINS-11381
> URL: https://issues.jenkins-ci.org/browse/JENKINS-11381
> Project: Jenkins
> Issue Type: Improvement
> Components: subversion
> Reporter: soundworker
> Priority: Critical
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
mattinger@gmail.com (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=155117#comment-155117 ]
Matthew Inger commented on JENKINS-11381:
-----------------------------------------
Why not allow usage of the command line client, instead of just SVNKit? At least this way, you're not always dependent on a particular downstream product?
> Subversion Plugin does not support Subversion 1.7
> -------------------------------------------------
>
> Key: JENKINS-11381
> URL: https://issues.jenkins-ci.org/browse/JENKINS-11381
> Project: Jenkins
> Issue Type: Improvement
> Components: subversion
> Reporter: soundworker
> Priority: Critical
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
doug.borg@integware.com (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=155427#comment-155427 ]
Doug Borg edited comment on JENKINS-11381 at 11/15/11 12:35 AM:
----------------------------------------------------------------
Implementing something like what @tjuerge suggests in JENKINS-2296 (using svnClientAdapter) for the SVN plugin would get you 1.7 support using the command-line option. This is probably not a trivial fix though.
http://subclipse.tigris.org/source/browse/subclipse/trunk/svnClientAdapter/readme.txt?view=markup
was (Author: dougborg):
Implementing something like what is suggested in JENKINS-2296 for the SVN plugin would get you 1.7 support. This is not a trivial fix though.
> Subversion Plugin does not support Subversion 1.7
> -------------------------------------------------
>
> Key: JENKINS-11381
> URL: https://issues.jenkins-ci.org/browse/JENKINS-11381
> Project: Jenkins
> Issue Type: Improvement
> Components: subversion
> Reporter: soundworker
> Priority: Critical
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
doug.borg@integware.com (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=155427#comment-155427 ]
Doug Borg edited comment on JENKINS-11381 at 11/15/11 12:38 AM:
----------------------------------------------------------------
Implementing something like what [~tjuerge] suggests in JENKINS-2296 (using svnClientAdapter) for the SVN plugin would get you 1.7 support using the command-line option. This is probably not a trivial fix though.
http://subclipse.tigris.org/source/browse/subclipse/trunk/svnClientAdapter/readme.txt?view=markup
was (Author: dougborg):
Implementing something like what @tjuerge suggests in JENKINS-2296 (using svnClientAdapter) for the SVN plugin would get you 1.7 support using the command-line option. This is probably not a trivial fix though.
http://subclipse.tigris.org/source/browse/subclipse/trunk/svnClientAdapter/readme.txt?view=markup
> Subversion Plugin does not support Subversion 1.7
> -------------------------------------------------
>
> Key: JENKINS-11381
> URL: https://issues.jenkins-ci.org/browse/JENKINS-11381
> Project: Jenkins
> Issue Type: Improvement
> Components: subversion
> Reporter: soundworker
> Priority: Critical
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
kai.virkki@gmail.com (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=155725#comment-155725 ]
Kai Virkki commented on JENKINS-11381:
--------------------------------------
Jenkins works fine with Subversion 1.7 if you use the HTTP protocol. The SVN protocol is broken due to a bug in SVNKIT: http://issues.tmatesoft.com/issue/SVNKIT-153
> Subversion Plugin does not support Subversion 1.7
> -------------------------------------------------
>
> Key: JENKINS-11381
> URL: https://issues.jenkins-ci.org/browse/JENKINS-11381
> Project: Jenkins
> Issue Type: Improvement
> Components: subversion
> Reporter: soundworker
> Priority: Critical
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
dccarson@gmail.com (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=156442#comment-156442 ]
David Carson commented on JENKINS-11381:
----------------------------------------
Note that SVNKit support for subversion 1.7 has two flavors. First, there is support for the 1.7 working copy format. This is not necessary to allow Jenkins to work with an svn 1.7 server.
The other problem is a bug with how SVNKit forms the URL when checking out code from an svn 1.7 server. THIS bug must be fixed before Jenkins can incorporate it.
I am happy to say that I checked SVNKit's site this morning, as I am as anxious as the rest of you. They have released 1.3.7, which claims to have fixed the URL bug. Now it is a matter of waiting until Jenkins has updated to the new SVNKit.
Here is the text from the SVNKit site:
Latest Stable Version
6 Dec 2011, 19:02, version 1.3.7
Changelog:
+ 1.7 Subversion servers compatibility issues fixed.
+ Export operation failed on missing directories, fixed.
* For new 1.7 Subversion working copy format support
please use SVNKit 1.7.0-alpha version.
> Subversion Plugin does not support Subversion 1.7
> -------------------------------------------------
>
> Key: JENKINS-11381
> URL: https://issues.jenkins-ci.org/browse/JENKINS-11381
> Project: Jenkins
> Issue Type: Improvement
> Components: subversion
> Reporter: soundworker
> Priority: Critical
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
stephane@odul.com (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stephane Odul updated JENKINS-11381:
------------------------------------
Priority: Blocker (was: Critical)
> Subversion Plugin does not support Subversion 1.7
> -------------------------------------------------
>
> Key: JENKINS-11381
> URL: https://issues.jenkins-ci.org/browse/JENKINS-11381
> Project: Jenkins
> Issue Type: Improvement
> Components: subversion
> Reporter: soundworker
> Priority: Blocker
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
emergency.shower@gmail.com (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=157033#comment-157033 ]
Alexander Veit commented on JENKINS-11381:
------------------------------------------
We are experiencing the same problem after an update to Subversion 1.7. Jenkins with over 120 projects all stands still for two weeks now.
Unfortunately switching to another protocol is not an option for us.
> Subversion Plugin does not support Subversion 1.7
> -------------------------------------------------
>
> Key: JENKINS-11381
> URL: https://issues.jenkins-ci.org/browse/JENKINS-11381
> Project: Jenkins
> Issue Type: Improvement
> Components: subversion
> Reporter: soundworker
> Priority: Blocker
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
matthias.ulrich@bct-technology.com (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=157040#comment-157040 ]
Matthias Ulrich commented on JENKINS-11381:
-------------------------------------------
We are delaying the update of our SVN Server due to this Issue and for several other reasons we really would like to update...
> Subversion Plugin does not support Subversion 1.7
> -------------------------------------------------
>
> Key: JENKINS-11381
> URL: https://issues.jenkins-ci.org/browse/JENKINS-11381
> Project: Jenkins
> Issue Type: Improvement
> Components: subversion
> Reporter: soundworker
> Priority: Blocker
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
jmsachs@gmail.com (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=157785#comment-157785 ]
Jason Sachs commented on JENKINS-11381:
---------------------------------------
>Why not allow usage of the command line client, instead of just SVNKit? At least this way, you're not always dependent on a particular downstream product?
I second this....
> Subversion Plugin does not support Subversion 1.7
> -------------------------------------------------
>
> Key: JENKINS-11381
> URL: https://issues.jenkins-ci.org/browse/JENKINS-11381
> Project: Jenkins
> Issue Type: Improvement
> Components: subversion
> Reporter: soundworker
> Priority: Blocker
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
roland@stackandheap.com (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159102#comment-159102 ]
Roland Zwaga commented on JENKINS-11381:
----------------------------------------
Is there some sort of ETA for this fix? I have quite a few projects that can no longer be built by Jenkins. I understand OS work is mostly done in people's spare time, but a rough estimate of when this can be fixed would be really appreciated.
Thanks a lot in advance.
> Subversion Plugin does not support Subversion 1.7
> -------------------------------------------------
>
> Key: JENKINS-11381
> URL: https://issues.jenkins-ci.org/browse/JENKINS-11381
> Project: Jenkins
> Issue Type: Improvement
> Components: subversion
> Reporter: soundworker
> Priority: Blocker
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
eaowens@gmail.com (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159123#comment-159123 ]
Evan Owens commented on JENKINS-11381:
--------------------------------------
>Why not allow usage of the command line client, instead of just SVNKit? At least this way, you're not always dependent on a particular downstream product?
I third this.
> Subversion Plugin does not support Subversion 1.7
> -------------------------------------------------
>
> Key: JENKINS-11381
> URL: https://issues.jenkins-ci.org/browse/JENKINS-11381
> Project: Jenkins
> Issue Type: Improvement
> Components: subversion
> Reporter: soundworker
> Priority: Blocker
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
kutzi@gmx.de (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159124#comment-159124 ]
kutzi commented on JENKINS-11381:
---------------------------------
>Why not allow usage of the command line client, instead of just SVNKit? At least this way, you're not always dependent on a particular downstream product?
In that case you're dependent on having the user installed the 'right' version of the native svn client. I'm not sure if that is the better alternative.
> Subversion Plugin does not support Subversion 1.7
> -------------------------------------------------
>
> Key: JENKINS-11381
> URL: https://issues.jenkins-ci.org/browse/JENKINS-11381
> Project: Jenkins
> Issue Type: Improvement
> Components: subversion
> Reporter: soundworker
> Priority: Blocker
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
jovanovic.milutin@gmail.com (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159216#comment-159216 ]
Milutin Jovanovic commented on JENKINS-11381:
---------------------------------------------
> Is there some sort of ETA for this fix?
Jenkins SVN depends on SVNKIT. They have been promising a new version for a while, but always ran into trouble. Currently their web site says release Feb 2012, but since they are about to release beta, I am guessing March. It's a guess. I am sure Jenkins SVN people will update the plugin as soon as the underlying library is updated.
> In that case you're dependent on having the user installed the 'right' version of the native svn client. I'm not sure if that is the better alternative.
It worked fine for Netbeans for months... Jumping through some hoops is prefereable to it not working at all. I fourth this.
> Subversion Plugin does not support Subversion 1.7
> -------------------------------------------------
>
> Key: JENKINS-11381
> URL: https://issues.jenkins-ci.org/browse/JENKINS-11381
> Project: Jenkins
> Issue Type: Improvement
> Components: subversion
> Reporter: soundworker
> Priority: Blocker
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
gustavo@cpqd.com.br (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159430#comment-159430 ]
Gustavo Chaves commented on JENKINS-11381:
------------------------------------------
> In that case you're dependent on having the user installed the 'right' version of the native svn client. I'm not sure if that is the better alternative.
What about a global or a job configuration option to let the user decide which svn client to use?
> Subversion Plugin does not support Subversion 1.7
> -------------------------------------------------
>
> Key: JENKINS-11381
> URL: https://issues.jenkins-ci.org/browse/JENKINS-11381
> Project: Jenkins
> Issue Type: Improvement
> Components: subversion
> Reporter: soundworker
> Priority: Blocker
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
chris.platts@gmail.com (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160639#comment-160639 ]
Chris Platts commented on JENKINS-11381:
----------------------------------------
Hi,
I've got a few projects which perform a svn commit as part of their build process (a script updates version numbers to match the build/revision before committing those changes back to the repository).
As a workaround, I've added an 'svn upgrade .' command before the 'svn commit .' statement. This means that the old-format working dir created by Jenkins is able to be committed at the end of the build.
This works, but almost doubles the time that each build takes. I'm really looking forward to an update to this plugin to support v1.7 working copies.
Of course, as mentioned, I'd also have no problem with an option to use the native svn client.
Thanks,
Chris
> Subversion Plugin does not support Subversion 1.7
> -------------------------------------------------
>
> Key: JENKINS-11381
> URL: https://issues.jenkins-ci.org/browse/JENKINS-11381
> Project: Jenkins
> Issue Type: Improvement
> Components: subversion
> Reporter: soundworker
> Priority: Blocker
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
jbeeckman@compliancesystems.com (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161188#comment-161188 ]
Jay Beeckman commented on JENKINS-11381:
----------------------------------------
Any update on this? It appears that SVNKIT has updated their stuff? An ETA would be great.
> Subversion Plugin does not support Subversion 1.7
> -------------------------------------------------
>
> Key: JENKINS-11381
> URL: https://issues.jenkins-ci.org/browse/JENKINS-11381
> Project: Jenkins
> Issue Type: Improvement
> Components: subversion
> Reporter: soundworker
> Priority: Blocker
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
jovanovic.milutin@gmail.com (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161189#comment-161189 ]
Milutin Jovanovic commented on JENKINS-11381:
---------------------------------------------
I am not the maintainer, but interested in this...
SVNKit is still in release candidate stage, so I don't think svn plugin will be updated until SVNKit is fully released.
jbeeckman@compliancesystems.com (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161388#comment-161388 ]
Jay Beeckman commented on JENKINS-11381:
----------------------------------------
This is according to SVNKit's web page (http://svnkit.com/download.php):
"Lastest stable version of SVNKit (1.3.7) is not compatible with Subversion 1.7 working copy format. However, SVNKit 1.7 is under development now and we plan to release it in 12th of April 2012. We plan to publish first Release Candidate build till the end of February 2012."
This is in three days, when could we reasonably expect this to be rolled into the plugin if they do indeed release on the 12th?
gustavo@cpqd.com.br (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161545#comment-161545 ]
Gustavo Chaves commented on JENKINS-11381:
------------------------------------------
SVNKit 1.7.4 has just been released. The [download page|http://svnkit.com/download.php] says this:
{quote}
Lastest stable version of SVNKit (*1.7.4*) is *compatible* with Subversion 1.7 working copy format and with Subversion 1.7 servers.
{quote}
tetdmi@gmail.com (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161631#comment-161631 ]
Dmitry Teterevyatnikov commented on JENKINS-11381:
--------------------------------------------------
Due to released SVNKit, do you have any plans to update Subversion plugin?
jtruelove@kingstreet.com (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161690#comment-161690 ]
J T commented on JENKINS-11381:
-------------------------------
Any updates on this? It appears there is a stable release of SVNKit which supports 1.7
qinding@softhinker.com (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161716#comment-161716 ]
Qin Ding commented on JENKINS-11381:
------------------------------------
There is my workaround :
1. Install the latest CollabNet Subversion Client to the server, which provides svn command-line tool.
2. Put all maven commands into a shell, i.e. bat for Windows.
3. Use maven-antrun-plugin to execute that shell.
4. In Jenkins configuration page, just use 'antrun:run' as the 'Goals and options'.
It works because the shell will use the system variable where PATH includes the latest CollabNet path rather than the old svn path used by Jenkins.
My website : http://softhinker.com
tetdmi@gmail.com (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161717#comment-161717 ]
Dmitry Teterevyatnikov commented on JENKINS-11381:
--------------------------------------------------
Your workaround seems good, but how you can replace Jenkins CI SVN checkout/update from SVN action? Current problem with SVN 1.7 support in Jenkins is: Jenkins will check-out/update project code from SVN 1.7 server in outdated SVN 1.6 file format and latest command-line SVN clients are not compatible with old SVN 1.6 file format
qinding@softhinker.com (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161716#comment-161716 ]
Qin Ding edited comment on JENKINS-11381 at 4/18/12 10:14 AM:
--------------------------------------------------------------
There is my workaround :
1. Install the latest CollabNet Subversion Client to the server, which provides svn command-line tool.
2. Put all maven commands into a shell, i.e. bat for Windows.
3. Use maven-antrun-plugin to execute that shell.
4. In Jenkins configuration page, just use 'antrun:run' as the 'Goals and options'.
It works because the shell will use the system variable where PATH includes the latest CollabNet path rather than the old svn path used by Jenkins.
My website describes more : http://www.softhinker.com/in-the-news/howtomakejenkinssupportsubversion17
was (Author: softhinker):
There is my workaround :
1. Install the latest CollabNet Subversion Client to the server, which provides svn command-line tool.
2. Put all maven commands into a shell, i.e. bat for Windows.
3. Use maven-antrun-plugin to execute that shell.
4. In Jenkins configuration page, just use 'antrun:run' as the 'Goals and options'.
It works because the shell will use the system variable where PATH includes the latest CollabNet path rather than the old svn path used by Jenkins.
My website : http://softhinker.com
jtruelove@kingstreet.com (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161730#comment-161730 ]
Jeremy Truelove commented on JENKINS-11381:
-------------------------------------------
Not everyone uses ant/maven
tetdmi@gmail.com (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161733#comment-161733 ]
Dmitry Teterevyatnikov commented on JENKINS-11381:
--------------------------------------------------
I am agree with Jeremy, i.e. everyone wants to use the Jenkins with all its features "from the box" with the best performance. Does anyone knows how to speedUp this issue to be resolved?
matthias.ulrich@bct-technology.com (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161735#comment-161735 ]
Matthias Ulrich commented on JENKINS-11381:
-------------------------------------------
I also want to point out, that the workaround is not applicable to all use cases of Jenkins and that this is a show stopper in some situation.
So as svnkit for svn1.7 is availble, this issue should be assigned as it is a showstopper/"Blocker".
matthias.ulrich@bct-technology.com (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161735#comment-161735 ]
Matthias Ulrich edited comment on JENKINS-11381 at 4/18/12 3:03 PM:
--------------------------------------------------------------------
I also want to point out, that the workaround is not applicable to all use cases of Jenkins and that this is a show stopper in some situations.
So as svnkit for svn 1.7 is availble now, this issue should be assigned as it is a "Blocker".
was (Author: mulrich):
klass@ite-web.de (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161737#comment-161737 ]
Jan Klass commented on JENKINS-11381:
-------------------------------------
@Dmitry:
The only thing you can do to speed up the process is
* vote on this issue (left of top right)
* fix / implement it yourself and commit / provide patch/diff
jbeeckman@compliancesystems.com (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161739#comment-161739 ]
Jay Beeckman commented on JENKINS-11381:
----------------------------------------
Jan, I have considered trying to get the fix in myself. If I wasn't so busy right now I would. This is holding up a big integration we have done with our delivery process, so it's killing me, but not something I could do right away. I do like your suggestion of voting, more voices the better :-)
Jay
jtruelove@kingstreet.com (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161741#comment-161741 ]
Jeremy Truelove commented on JENKINS-11381:
-------------------------------------------
Are there any plans going forward to decouple Jenkins from specific svn versions, i.e. allow the user to specify the executable? Like what is done for git etc...
jpress@planetenergy.ca (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161800#comment-161800 ]
Jamie Press commented on JENKINS-11381:
---------------------------------------
SVNKit 1.7.4 is now out, which does allow functionality with both 1.7 server and working copies...
/hopeful glance?
tetdmi@gmail.com (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161888#comment-161888 ]
Dmitry Teterevyatnikov commented on JENKINS-11381:
--------------------------------------------------
Looks like Jenkins Jira is "dead"... really strange for a so popular service/product. Does anyone knows how to force this issue to be resolved (together with voiting)?
mark.dreyer@redprairie.com (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161893#comment-161893 ]
Mark Dreyer commented on JENKINS-11381:
---------------------------------------
The hudson team did some work on this that included removing the customization to svn kit. If the same can be done with jenkins, you could just use the new svnkit library.
See http://issues.hudson-ci.org/browse/HUDSON-9111 for more info.
jpress@planetenergy.ca (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161894#comment-161894 ]
Jamie Press commented on JENKINS-11381:
---------------------------------------
In JENKINS-11933, the 'duplicate' issue for this, someone added a patch file that theoretically upgrades the svnkit version from the defective 1.3.6.1 to the partially working 1.3.7 (this version can apparently speak to the 1.7.x server, though not 1.7.x working copy).
As I would guess that most of us are only using Jenkins to check out the latest version, this may serve as a workaround for many. However, applying a patch file is a little beyond my expertise. Is anyone able to see if that patch works, and if so, post the patched svnkit? It apparently makes a version called 1.3.7-jenkins-0.
All that being said, Dreyguy is right in saying the Hudson team made the right move. Decoupling the svnkit from the plugin would be desirable.
centic@java.net (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161902#comment-161902 ]
centic commented on JENKINS-11381:
----------------------------------
I have now attached the .hpi file that I use locally for getting at least 1.7-server supported in Jenkins to JENKINS-11933.
nezah@solbox.com (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161910#comment-161910 ]
hyunsoo lee commented on JENKINS-11381:
---------------------------------------
Thanks a lot!!! centic!!
It's working
tetdmi@gmail.com (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161914#comment-161914 ]
Dmitry Teterevyatnikov commented on JENKINS-11381:
--------------------------------------------------
@centric: Thanks for the patch. But it looks like even with your patch we still have a problem with full SVN 1.7 support by Jenkins.
I.e. currently on our build environments, Jenkins works fine with SVN 1.7 with old 1.6 SVN format. Everithing works correct, but.. performance of all SVN related operations is horrible. I.e. checkout of SVN 1.7 trunk by Jenkins with size about 100 MB takes about 30-40 minutes. Due to SVN 1.6 working format is used by current version of Jenkins SVN plugin, newest command-line SVN clients works with old SVN 1.6 format really slow. At the result our releases takes more then hour, where 40 minutes - it is a SVN-related tasks.
I am totally sure that update of Subversion plugin on Jenkins to latest SVNKit will fix all SVN performance re;lated problems.
centic@java.net (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161969#comment-161969 ]
centic commented on JENKINS-11381:
----------------------------------
Sorry, I already gave it a try and started the merge of 1.7.4 and the jenkins-specific changes, but there are a lot of conflicts and I lack some knowledge about the changes in the jenkins-version to tell me how to solve them... Maybe I try again and see if a hacky-wacky merge leads at least to a workable solution...
k_kartikeya@yahoo.com (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162009#comment-162009 ]
Kumar Kartikeya commented on JENKINS-11381:
-------------------------------------------
I tried replacing old current jars in /plugins/subversion/WEB-INF/lib/ with sequence-library-1.0.1.jar svnkit-1.7.4.jar, but getting following
FATAL: org/tmatesoft/svn/core/auth/ISVNAuthenticationOutcomeListener
java.lang.NoClassDefFoundError: org/tmatesoft/svn/core/auth/ISVNAuthenticationOutcomeListener
centic@java.net (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162022#comment-162022 ]
centic commented on JENKINS-11381:
----------------------------------
I'll try to post an updated hack-build of the plugin and put all the necessary changes (svnkit/trilead-ssh2/subversion-plugin) on github so they can be reviewed and applied to the official sources easily. (I am not associated with any of these projects currently, so I cannot do offical builds here)
centic@java.net (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162045#comment-162045 ]
centic commented on JENKINS-11381:
----------------------------------
tetdmi@gmail.com (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162079#comment-162079 ]
Dmitry Teterevyatnikov commented on JENKINS-11381:
--------------------------------------------------
This Jira is the most voted blocker in this project, why it is not assigned to anyone who have rights to include fixes in the product?
heinzepreller@gmail.com (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162081#comment-162081 ]
Robert Lachner commented on JENKINS-11381:
------------------------------------------
One Question:
Do i really have to wait for a working 1.7.4 SVN Plugin for JIRA ? If i use Jenkins against 1.7.4 SVN with 1.6 Plugin everything works fine except that the checked out workspaces are in the old 1.6 svn format. Are there any problems that i don't see ?
tetdmi@gmail.com (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162082#comment-162082 ]
Dmitry Teterevyatnikov commented on JENKINS-11381:
--------------------------------------------------
heinzepreller@gmail.com (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162083#comment-162083 ]
Robert Lachner commented on JENKINS-11381:
------------------------------------------
ok, just tried 60MB checkout on a Virtual Machine with Jenkins 1.461, SVN Plugin 1.34 and VisualSVN 2.5.4(the Version with SVN 1.7.4), it takes about 30seconds.
Nothing unusual so far...
Maybe the older 1.34 Version does not have this long checkout behaviour ?
heinzepreller@gmail.com (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162083#comment-162083 ]
Robert Lachner edited comment on JENKINS-11381 at 4/26/12 10:53 AM:
--------------------------------------------------------------------
@Dimitry
ok, just tried 60MB checkout on a Virtual Machine with Jenkins 1.461, SVN Plugin 1.34 and VisualSVN 2.5.4(the Version with SVN 1.7.4), it takes about 30seconds.
Nothing unusual so far...
Maybe the older 1.34 Version does not have this long checkout behaviour ?
was (Author: heinzepreller0815):
jbuchberger@java.net (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162086#comment-162086 ]
jbuchberger commented on JENKINS-11381:
---------------------------------------
FWIW, svnkit 1.7.4 hit maven central and should be generally available
ntumba.lobo3@gmail.com (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162378#comment-162378 ]
ntumba lobo commented on JENKINS-11381:
---------------------------------------
Are we soon going to have a fix in the product for this issue ?
I cannot do maven releases because of this....
richard.villanueva@ainidit.Fr (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162439#comment-162439 ]
Richard Villanueva commented on JENKINS-11381:
----------------------------------------------
Hi,
We also are waiting for this update for 2 months, it should be great because of the SVN migration is postponed until the compatibility between our Jenkins platform and our new SVN plaform is made;
Good luke for the final lap of merging your work in the next release of Jenkins
Regards
Richard
kk@kohsuke.org (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kohsuke Kawaguchi updated JENKINS-11381:
----------------------------------------
Attachment: subversion.hpi
Uploaded 1.40 RC that supports Subversion 1.7
> Subversion Plugin does not support Subversion 1.7
> -------------------------------------------------
>
> Key: JENKINS-11381
> URL: https://issues.jenkins-ci.org/browse/JENKINS-11381
> Project: Jenkins
> Issue Type: Improvement
> Components: subversion
> Reporter: soundworker
> Priority: Blocker
kk@kohsuke.org (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162502#comment-162502 ]
Kohsuke Kawaguchi edited comment on JENKINS-11381 at 5/7/12 8:38 PM:
---------------------------------------------------------------------
[Uploaded 1.40 RC|https://issues.jenkins-ci.org/secure/attachment/21796/subversion.hpi] that supports Subversion 1.7. I'm running this on http://ci.jenkins-ci.org/ now, but any additional beta testing appreciated.
It does pass all the tests we have, but there are major changes in SVNKit, so I'm being bit cautious.
was (Author: kohsuke):
ukrainial@gmail.com (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162505#comment-162505 ]
Alexei Turchanikov commented on JENKINS-11381:
----------------------------------------------
I just tried the 1.40 RC, it throws an exception when attempting to check out to a directory that isn't a working copy (such as when "Always check out a fresh copy" is selected or if this is the first build):
ERROR: Failed to check out https://domain/svn/repo
org.tmatesoft.svn.core.SVNException: svn: E155007: 'C:\Data\Jenkins\workspace\job\src' is not a working copy
at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64)
at org.tmatesoft.svn.core.internal.wc.admin.SVNAdminAreaFactory.open(SVNAdminAreaFactory.java:170)
at org.tmatesoft.svn.core.internal.wc.admin.SVNWCAccess.doOpen(SVNWCAccess.java:379)
at org.tmatesoft.svn.core.internal.wc.admin.SVNWCAccess.open(SVNWCAccess.java:283)
at org.tmatesoft.svn.core.internal.wc.admin.SVNWCAccess.open(SVNWCAccess.java:276)
at org.tmatesoft.svn.core.internal.wc.admin.SVNWCAccess.openAnchor(SVNWCAccess.java:171)
at org.tmatesoft.svn.core.internal.wc16.SVNUpdateClient16.update(SVNUpdateClient16.java:514)
at org.tmatesoft.svn.core.internal.wc16.SVNUpdateClient16.doCheckout(SVNUpdateClient16.java:965)
at org.tmatesoft.svn.core.internal.wc2.old.SvnOldCheckout.run(SvnOldCheckout.java:19)
at org.tmatesoft.svn.core.internal.wc2.old.SvnOldCheckout.run(SvnOldCheckout.java:8)
at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:20)
at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1221)
at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:292)
at org.tmatesoft.svn.core.wc.SVNUpdateClient.doCheckout(SVNUpdateClient.java:781)
at hudson.scm.subversion.CheckoutUpdater$1.perform(CheckoutUpdater.java:86)
at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:144)
at hudson.scm.SubversionSCM$CheckOutTask.perform(SubversionSCM.java:789)
at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:770)
at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:753)
at hudson.FilePath.act(FilePath.java:832)
at hudson.FilePath.act(FilePath.java:814)
at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:743)
at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:685)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1218)
at hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:581)
at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:470)
at hudson.model.Run.run(Run.java:1434)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:239)
Caused by: svn: E155007: 'C:\Data\Jenkins\workspace\job\src' is not a working copy
at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:171)
at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:126)
at org.tmatesoft.svn.core.internal.wc.admin.SVNAdminAreaFactory.open(SVNAdminAreaFactory.java:165)
... 28 more
FATAL: null
java.lang.NullPointerException
at java.util.ArrayList.addAll(Unknown Source)
at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:743)
at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:685)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1218)
at hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:581)
at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:470)
at hudson.model.Run.run(Run.java:1434)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:239)
kk@kohsuke.org (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162522#comment-162522 ]
Kohsuke Kawaguchi commented on JENKINS-11381:
---------------------------------------------
Alexei, I couldn't reproduce the problem.
When this error happens, do you have C:\Data\Jenkins\workspace\job\src\.svn? I step executed the code and it does create the workspace right before the code gets to here.
The other experiment I'd like you to try is to use the scripting console, run "org.tmatesoft.svn.core.internal.wc.admin.SVNAdminAreaFactory.ourFactories;", and report back what you see. I wonder if someone else is setting that collection to empty, which would explain this.
I continue to look for other people trying out this version.
john.salvo@aas.com.au (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162534#comment-162534 ]
John Salvo commented on JENKINS-11381:
--------------------------------------
Out of curiosity, those experiencing long delays during any SVN operation when they upgraded their SVN plugin to use 1.7/1.8 format .. did you upgrade your working copy from 1.6 to 1.7/1.8 format first ?
http://subversion.apache.org/docs/release-notes/1.7.html#wc-ng
To quote:
"Upgrading the Working Copy
Subversion 1.7 introduces substantial changes to the working copy format. In previous releases of Subversion, Subversion would automatically update the working copy to the new format when a write operation was performed. Subversion 1.7, however, will make this a manual step. Before using Subversion 1.7 with their working copies, users will be required to run a new command, svn upgrade to update the metadata to the new format. This command may take a while, and for some users, it may be more practical to simply checkout a new working copy."
john.salvo@aas.com.au (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162534#comment-162534 ]
John Salvo edited comment on JENKINS-11381 at 5/8/12 11:21 AM:
---------------------------------------------------------------
Out of curiosity, those experiencing long delays during any SVN operation when they upgraded their SVN plugin to use 1.7 format .. did you upgrade your working copy from 1.6 to 1.7 format first ?
http://subversion.apache.org/docs/release-notes/1.7.html#wc-ng
To quote:
"Upgrading the Working Copy
Subversion 1.7 introduces substantial changes to the working copy format. In previous releases of Subversion, Subversion would automatically update the working copy to the new format when a write operation was performed. Subversion 1.7, however, will make this a manual step. Before using Subversion 1.7 with their working copies, users will be required to run a new command, svn upgrade to update the metadata to the new format. This command may take a while, and for some users, it may be more practical to simply checkout a new working copy."
peter@kode.cc (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162535#comment-162535 ]
Peter Lillevold commented on JENKINS-11381:
-------------------------------------------
The question is: will the new SVNKit do an automatic working copy upgrade? Or are we better of scrapping all our existing working copies?
klass@ite-web.de (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162536#comment-162536 ]
Jan Klass commented on JENKINS-11381:
-------------------------------------
An automatic upgrade should definitely not be the way to go, as workspaces, tool- and build-chains may depend on the old working copy structure.
Maybe a flag setting for enabling an automatic upgrade when the old format is identified would be an option.
brenuart@java.net (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162538#comment-162538 ]
brenuart commented on JENKINS-11381:
------------------------------------
Don't see any benefit of having such an "auto upgrade" feature...
What's the problem in just dropping the workspaces and let Jenkins checkout the projects again ?
It's just a one-time operation...
cynic783@gmail.com (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162542#comment-162542 ]
Dan Lewis commented on JENKINS-11381:
-------------------------------------
agree. bonus points if we can fail fast with an appropriate error message explaining corrective procedure, e.g. "jenkins does not support auto-update of pre-SVN 1.7 workspaces to 1.7; please remove workspaces and restart build" or some such
klass@ite-web.de (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162543#comment-162543 ]
Jan Klass commented on JENKINS-11381:
-------------------------------------
The parametrized build (List subversion tags and more) only lists trunk.
See also the other ticket https://issues.jenkins-ci.org/browse/JENKINS-11933?focusedCommentId=162399#comment-162399
On Configuration: The repository is being accepted as valid, root path as well as subpaths. Did not check out on it yet.
klass@ite-web.de (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162544#comment-162544 ]
Jan Klass commented on JENKINS-11381:
-------------------------------------
The URI was a subpath of trunk, so not trunk itself.
{quote}
Checking out a fresh workspace because C:\jenkins\workspace\ProjName\MyFolder doesn't exist
Cleaning local Directory MyFolder
Checking out svn://srv/repopath/trunk/MyFolder
ERROR: Failed to check out svn://srv/repopath/trunk/MyFolder
org.tmatesoft.svn.core.SVNException: svn: E155007: 'C:\jenkins\workspace\ProjName\MyFolder ' is not a working copy
{quote}
klass@ite-web.de (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162544#comment-162544 ]
Jan Klass edited comment on JENKINS-11381 at 5/8/12 3:12 PM:
-------------------------------------------------------------
I just tried to check out a fresh copy, which did not succeed.
The URI was a subpath of trunk, so not trunk itself.
{quote}
Checking out a fresh workspace because C:\jenkins\workspace\ProjName\MyFolder doesn't exist
Cleaning local Directory MyFolder
Checking out svn://srv/repopath/trunk/MyFolder
ERROR: Failed to check out svn://srv/repopath/trunk/MyFolder
org.tmatesoft.svn.core.SVNException: svn: E155007: 'C:\jenkins\workspace\ProjName\MyFolder ' is not a working copy
{quote}
was (Author: jk):
klass@ite-web.de (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162544#comment-162544 ]
Jan Klass edited comment on JENKINS-11381 at 5/8/12 3:12 PM:
-------------------------------------------------------------
I just tried to check out a fresh copy, which did not succeed.
The URI was a subpath of trunk, so not trunk itself.
{quote}
Checking out a fresh workspace because C:\jenkins\workspace\ProjName\MyFolder doesn't exist
Cleaning local Directory MyFolder
Checking out svn://srv/repopath/trunk/MyFolder
ERROR: Failed to check out svn://srv/repopath/trunk/MyFolder
org.tmatesoft.svn.core.SVNException: svn: E155007: 'C:\jenkins\workspace\ProjName\MyFolder ' is not a working copy
{quote}
klass@ite-web.de (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162544#comment-162544 ]
Jan Klass edited comment on JENKINS-11381 at 5/8/12 3:14 PM:
I just tried to check out a fresh copy, which did not succeed.
The URI was a subpath of trunk, so not trunk itself.
{quote}
Checking out a fresh workspace because C:\jenkins\workspace\ProjName\MyFolder doesn't exist
Cleaning local Directory MyFolder
Checking out svn://srv/repopath/trunk/MyFolder
ERROR: Failed to check out svn://srv/repopath/trunk/MyFolder
org.tmatesoft.svn.core.SVNException: svn: E155007: 'C:\jenkins\workspace\ProjName\MyFolder ' is not a working copy
{quote}
Checking out to a 1.6 workspace instead of 1.7 worked with the same configuration.
Checking out trunk to a 1.7 workspace fails as well, same error.
was (Author: jk):
I just tried to check out a fresh copy, which did not succeed.
The URI was a subpath of trunk, so not trunk itself.
{quote}
Checking out a fresh workspace because C:\jenkins\workspace\ProjName\MyFolder doesn't exist
Cleaning local Directory MyFolder
Checking out svn://srv/repopath/trunk/MyFolder
ERROR: Failed to check out svn://srv/repopath/trunk/MyFolder
org.tmatesoft.svn.core.SVNException: svn: E155007: 'C:\jenkins\workspace\ProjName\MyFolder ' is not a working copy
{quote}
klass@ite-web.de (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162544#comment-162544 ]
Jan Klass edited comment on JENKINS-11381 at 5/8/12 3:54 PM:
I just tried to check out a fresh copy, which did not succeed.
The URI was a subpath of trunk, so not trunk itself.
{quote}
Checking out a fresh workspace because C:\jenkins\workspace\ProjName\MyFolder doesn't exist
Cleaning local Directory MyFolder
Checking out svn://srv/repopath/trunk/MyFolder
ERROR: Failed to check out svn://srv/repopath/trunk/MyFolder
org.tmatesoft.svn.core.SVNException: svn: E155007: 'C:\jenkins\workspace\ProjName\MyFolder ' is not a working copy
{quote}
Checking out to a 1.6 workspace instead of 1.7 worked with the same configuration.
/e:
Checking out trunk to a 1.7 workspace fails as well, same error.
Checking out a 1.7 working copy manually - to the target path - before the build starts (so, without jenkins),
jenkins does run an update on the working copy, the checked out path.
Going back to an older revision on the 1.7 working copy Jenkins does indeed update to HEAD.
Just the new checkout to 1.7 workspace seems to fail.
kk@kohsuke.org (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162546#comment-162546 ]
Kohsuke Kawaguchi commented on JENKINS-11381:
---------------------------------------------
Jan, what is the Subversion server version? You said you saw that error while you were checking out to 1.7 workspace format? Also, please don't truncate the stack trace, because it is invaluable for me to understand where things failed.
klass@ite-web.de (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162547#comment-162547 ]
Jan Klass commented on JENKINS-11381:
-------------------------------------
> When this error happens, do you have C:\Data\Jenkins\workspace\job\src\.svn? I step executed the code and it does create the workspace right before the code gets to here.
Even if I create the target folder myself, no .svn folder is being created.
> The other experiment I'd like you to try is to use the scripting console, run "org.tmatesoft.svn.core.internal.wc.admin.SVNAdminAreaFactory.ourFactories;", and report back what you see. I wonder if someone else is setting that collection to empty, which would explain this.
Result: [org.tmatesoft.svn.core.internal.wc.admin.SVNAdminArea16Factory@1b4d6c0, org.tmatesoft.svn.core.internal.wc.admin.SVNAdminArea15Factory@17f0649, org.tmatesoft.svn.core.internal.wc.admin.SVNAdminArea14Factory@75c229, org.tmatesoft.svn.core.internal.wc.admin.SVNXMLAdminAreaFactory@11e4232]
{quote}
klass@ite-web.de (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162547#comment-162547 ]
Jan Klass edited comment on JENKINS-11381 at 5/8/12 3:58 PM:
-------------------------------------------------------------
On the questions Kohsuke asked:
No. Neither the .svn folder nor the folder it should be placed in is being created.
Even if I create the target folder myself, no .svn folder is being created.
{quote}
Result: [org.tmatesoft.svn.core.internal.wc.admin.SVNAdminArea16Factory@1b4d6c0, org.tmatesoft.svn.core.internal.wc.admin.SVNAdminArea15Factory@17f0649, org.tmatesoft.svn.core.internal.wc.admin.SVNAdminArea14Factory@75c229, org.tmatesoft.svn.core.internal.wc.admin.SVNXMLAdminAreaFactory@11e4232]
{quote}
klass@ite-web.de (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162550#comment-162550 ]
Jan Klass commented on JENKINS-11381:
-------------------------------------
MyFolder1 is a 1.7 working copy I checked out manually before-hand.
MyFolder2 is the Path it is supposed to check out as a 1.7 working copy.
{quote}
Gestartet durch Benutzer anonymous
Baue auf Slave local2 in workspace c:\jenkins\workspace\Proj Name
Updating svn://srv/path/ProjRepo/trunk/MyFolder1
At revision 32522
Checking out a fresh workspace because there's no workspace at C:\jenkins\workspace\Proj Name\MyFolder2
Cleaning local Directory MyFolder2
Checking out svn://srv/path/ProjRepo/trunk/MyFolder2
ERROR: Failed to check out svn://srv/path/ProjRepo/trunk/MyFolder2
org.tmatesoft.svn.core.SVNException: svn: E155007: 'C:\jenkins\workspace\Proj Name\MyFolder2' is not a working copy
at org.tmatesoft.svn.core.internal.wc.admin.SVNAdminAreaFactory.open(SVNAdminAreaFactory.java:170)
at org.tmatesoft.svn.core.internal.wc.admin.SVNWCAccess.doOpen(SVNWCAccess.java:379)
at org.tmatesoft.svn.core.internal.wc.admin.SVNWCAccess.open(SVNWCAccess.java:283)
at org.tmatesoft.svn.core.internal.wc.admin.SVNWCAccess.open(SVNWCAccess.java:276)
at org.tmatesoft.svn.core.internal.wc.admin.SVNWCAccess.openAnchor(SVNWCAccess.java:171)
at org.tmatesoft.svn.core.internal.wc16.SVNUpdateClient16.update(SVNUpdateClient16.java:514)
at org.tmatesoft.svn.core.internal.wc16.SVNUpdateClient16.doCheckout(SVNUpdateClient16.java:965)
at org.tmatesoft.svn.core.internal.wc2.old.SvnOldCheckout.run(SvnOldCheckout.java:19)
at org.tmatesoft.svn.core.internal.wc2.old.SvnOldCheckout.run(SvnOldCheckout.java:8)
at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:20)
at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1221)
at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:292)
at org.tmatesoft.svn.core.wc.SVNUpdateClient.doCheckout(SVNUpdateClient.java:781)
at hudson.scm.subversion.CheckoutUpdater$1.perform(CheckoutUpdater.java:86)
at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:144)
at hudson.scm.subversion.UpdateUpdater$TaskImpl.perform(UpdateUpdater.java:121)
at hudson.scm.SubversionSCM$CheckOutTask.perform(SubversionSCM.java:789)
at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:770)
at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:753)
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:287)
at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at hudson.remoting.Engine$1$1.run(Engine.java:60)
at java.lang.Thread.run(Unknown Source)
Caused by: svn: E155007: 'C:\jenkins\workspace\Proj Name\MyFolder2' is not a working copy
at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:126)
at org.tmatesoft.svn.core.internal.wc.admin.SVNAdminAreaFactory.open(SVNAdminAreaFactory.java:165)
java.lang.NullPointerException
at java.util.ArrayList.addAll(Unknown Source)
at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:743)
at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:685)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1218)
at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:475)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:239)
kk@kohsuke.org (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162552#comment-162552 ]
Kohsuke Kawaguchi commented on JENKINS-11381:
---------------------------------------------
Looking into it.
kk@kohsuke.org (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162553#comment-162553 ]
Kohsuke Kawaguchi commented on JENKINS-11381:
---------------------------------------------
* version of the Subversion server (>=1.7 or <1.7?)
* working copy format you set in the global configuration
* Subversion access protocol
kk@kohsuke.org (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kohsuke Kawaguchi updated JENKINS-11381:
----------------------------------------
Attachment: subversion.hpi
> Subversion Plugin does not support Subversion 1.7
> -------------------------------------------------
>
> Key: JENKINS-11381
> URL: https://issues.jenkins-ci.org/browse/JENKINS-11381
> Project: Jenkins
> Issue Type: Improvement
> Components: subversion
> Reporter: soundworker
> Priority: Blocker
kk@kohsuke.org (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162556#comment-162556 ]
Kohsuke Kawaguchi edited comment on JENKINS-11381 at 5/8/12 5:17 PM:
---------------------------------------------------------------------
[Attached 1.40 RC2|https://issues.jenkins-ci.org/secure/attachment/21802/subversion.hpi] built from rev.40558 in the repository. This version fixes the checkout failure problem with 1.7 server + 1.7 working copy.
was (Author: kohsuke):
kk@kohsuke.org (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kohsuke Kawaguchi updated JENKINS-11381:
----------------------------------------
Attachment: subversion.hpi
> Subversion Plugin does not support Subversion 1.7
> -------------------------------------------------
>
> Key: JENKINS-11381
> URL: https://issues.jenkins-ci.org/browse/JENKINS-11381
> Project: Jenkins
> Issue Type: Improvement
> Components: subversion
> Reporter: soundworker
> Priority: Blocker
kk@kohsuke.org (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162557#comment-162557 ]
Kohsuke Kawaguchi edited comment on JENKINS-11381 at 5/8/12 5:33 PM:
---------------------------------------------------------------------
And [this is 1.40 RC3|https://issues.jenkins-ci.org/secure/attachment/21803/subversion.hpi] that fixes the "list tags/branches" parameter problem. From the repository revision 40560.
was (Author: kohsuke):
klass@ite-web.de (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162593#comment-162593 ]
Jan Klass commented on JENKINS-11381:
-------------------------------------
Will try out the new RC.
klass@ite-web.de (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162593#comment-162593 ]
Jan Klass edited comment on JENKINS-11381 at 5/9/12 7:07 AM:
-------------------------------------------------------------
On my RC1 problem: SVN version is 1.7 as well (thought you wanted a more specific version). Just as working copy format in global configuration, which is 1.7 as well. Accessed via svn protocol.
Will try out the new RC.
klass@ite-web.de (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162599#comment-162599 ]
Jan Klass commented on JENKINS-11381:
-------------------------------------
The tag-listing seems to work fine as well, they are listed as described. Checking a selected tag out to a 1.7 working copy seems to work fine as well. (I did not try selecting from the repo root but from a tags/branches folder as we have them not in first path level of tags/branches.)
klass@ite-web.de (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162600#comment-162600 ]
Jan Klass commented on JENKINS-11381:
-------------------------------------
looking forward to the release!
kk@kohsuke.org (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kohsuke Kawaguchi resolved JENKINS-11381.
-----------------------------------------
Assignee: Kohsuke Kawaguchi
Resolution: Fixed
Released as 1.40.
> Subversion Plugin does not support Subversion 1.7
> -------------------------------------------------
>
> Key: JENKINS-11381
> URL: https://issues.jenkins-ci.org/browse/JENKINS-11381
> Project: Jenkins
> Issue Type: Improvement
> Components: subversion
> Reporter: soundworker
pancake@java.net (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162965#comment-162965 ]
pancake commented on JENKINS-11381:
-----------------------------------
Please take a look at JENKINS-13835.
ntumba.lobo3@gmail.com (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163000#comment-163000 ]
ntumba lobo commented on JENKINS-11381:
---------------------------------------
Thank for the work on this issue.
I would benefit from it but I dont understand the release number mentioned by Kohsuke Kawaguchi 1.40.
What does it refer to ? Our current Jenkins version is already 1.447.
brenuart@java.net (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163002#comment-163002 ]
brenuart commented on JENKINS-11381:
------------------------------------
1.40 is the version of the *Subversion Plugin*. Go into "Manage Jenkins"->"Manage Plugins": the "Installed" tab lists the plugins installed on your instance and their corresponding versions.
duncan.perrett@gmail.com (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163004#comment-163004 ]
Duncan Perrett commented on JENKINS-11381:
------------------------------------------
I found it a bit confusing as the subversion plugin is one that is bundled with jenkins.
However, the latest jenkins.war bundle includes a much older version of the subversion plugin so you need to manually update it.
(I don't know when/if the bundled version will ever reach 1.40).
I think this is called 'pinning' the plugin.
wills.diane@con-way.com (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163491#comment-163491 ]
Diane Wills commented on JENKINS-11381:
---------------------------------------
I'm still not able to update Jenkins to use the Subversion Plugin 1.40. I'm using Jenkins 1.466 on Windows Server 2008. I tried manually updating the Subversion files and writing the empty file Subversion.jpi.pinned to $(JENKINS_HOME)/plugins, but that didn't work; the files got overwritten anyways to the old version.
Since there are no plans to add Subversion 1.40 to Jenkins permanently, can someone help me?
richard.villanueva@ainidit.Fr (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Richard Villanueva updated JENKINS-11381:
-----------------------------------------
It is not resolved
richard.villanueva@ainidit.Fr (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Richard Villanueva reopened JENKINS-11381:
------------------------------------------
denis.eperonnier@tremec.com (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163826#comment-163826 ]
Denis Eperonnier commented on JENKINS-11381:
--------------------------------------------
I noticed something strange using Subversion Plugin 1.40, together with Jenkins 1.467.
Some time after the upgrade from plugin 1.39, there were some errors when trying to update a slave workspace:
org.tmatesoft.svn.core.SVNException: svn: E175002: REPORT /svn/xxxxxxxxxx/!svn/vcc/default failed
at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:304)
at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:289)
at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:277)
at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:696)
at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.doReport(DAVConnection.java:328)
at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.runReport(DAVRepository.java:1289)
at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.update(DAVRepository.java:837)
at org.tmatesoft.svn.core.internal.wc16.SVNUpdateClient16.update(SVNUpdateClient16.java:557)
at org.tmatesoft.svn.core.internal.wc16.SVNUpdateClient16.doUpdate(SVNUpdateClient16.java:414)
at org.tmatesoft.svn.core.internal.wc16.SVNUpdateClient16.doUpdate(SVNUpdateClient16.java:324)
at org.tmatesoft.svn.core.internal.wc2.old.SvnOldUpdate.run(SvnOldUpdate.java:27)
at org.tmatesoft.svn.core.internal.wc2.old.SvnOldUpdate.run(SvnOldUpdate.java:11)
at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1221)
at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:292)
at org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:295)
at org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:391)
at hudson.scm.subversion.UpdateUpdater$TaskImpl.perform(UpdateUpdater.java:136)
at hudson.scm.SubversionSCM$CheckOutTask.perform(SubversionSCM.java:789)
at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:770)
at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:753)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:287)
at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at hudson.remoting.Engine$1$1.run(Engine.java:60)
at java.lang.Thread.run(Unknown Source)
at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:208)
at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:154)
at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:97)
... 34 more
no change for http://xxxxxxxxx since the previous build
So I checked svn server log, and I could see that my master node uses the latest SVNKit 1.7.4 ("SVN/1.7.4 SVNKit/1.7.4-jenkins-1 (http://svnkit.com/) t20120507_1224"), but one of my slaves is using an older version ("SVN/1.7.0 SVNKit/1.7.0-dev (http://svnkit.com/) rSNAPSHOT"), can this explain my issue?
denis.eperonnier@tremec.com (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163826#comment-163826 ]
Denis Eperonnier edited comment on JENKINS-11381 at 6/11/12 9:10 PM:
---------------------------------------------------------------------
I noticed something strange using Subversion Plugin 1.40, together with Jenkins 1.467.
Some time after the upgrade from plugin 1.39, there were some errors when trying to update a slave workspace:
So I checked svn server log, and I could see that my master node uses the latest SVNKit 1.7.4 ("SVN/1.7.4 SVNKit/1.7.4-jenkins-1 (http://svnkit.com/) t20120507_1224"), but one of my slaves is using an older version ("SVN/1.7.0 SVNKit/1.7.0-dev (http://svnkit.com/) rSNAPSHOT"), can this explain my issue?