Quantcast

[JIRA] (JENKINS-11933) Subversion plugin doesn't probably work correctly with svn server version 1.7.1

classic Classic list List threaded Threaded
40 messages Options
12
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[JIRA] (JENKINS-11933) Subversion plugin doesn't probably work correctly with svn server version 1.7.1

JIRA noreply@jenkins-ci.org
Nikita Aznauryan created JENKINS-11933:
------------------------------------------

             Summary: Subversion plugin doesn't probably work correctly with svn server version 1.7.1
                 Key: JENKINS-11933
                 URL: https://issues.jenkins-ci.org/browse/JENKINS-11933
             Project: Jenkins
          Issue Type: Bug
          Components: subversion
    Affects Versions: current
         Environment: svn server 1.7.1
ubuntu
            Reporter: Nikita Aznauryan
            Priority: Blocker


I use usernames in my svn path like:

svn+ssh://jenkins@somepath

but I get a warning "... doesn't exist in the repository"

I think it started after svn server has been updated to 1.7.1 version

It worked fine before.

Subversion pooling log :

Started on Nov 30, 2011 8:11:31 PM
Location 'svn+ssh://jenkins@path' does not exist
One or more repository locations do not exist anymore for hudson.model.FreeStyleProject@3937bf4[], project will be disabled.
Done. Took 1.3 sec
No changes


--
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
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[JIRA] (JENKINS-11933) Subversion plugin doesn't probably work correctly with svn server version 1.7.1

JIRA noreply@jenkins-ci.org

    [ https://issues.jenkins-ci.org/browse/JENKINS-11933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=156241#comment-156241 ]

Kohsuke Kawaguchi commented on JENKINS-11933:
---------------------------------------------

And does the path in question exist and accessible to you?

Given the way svn+ssh works, which is basically just "ssh jenkins@server svnserve repo", I find it rather unlikely that this breaks just because the server was upgraded.
               

> Subversion plugin doesn't probably work correctly with svn server version 1.7.1
> -------------------------------------------------------------------------------
>
>                 Key: JENKINS-11933
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-11933
>             Project: Jenkins
>          Issue Type: Bug
>          Components: subversion
>    Affects Versions: current
>         Environment: svn server 1.7.1
> ubuntu
>            Reporter: Nikita Aznauryan
>            Priority: Blocker
>
> I use usernames in my svn path like:
> svn+ssh://jenkins@somepath
> but I get a warning "... doesn't exist in the repository"
> I think it started after svn server has been updated to 1.7.1 version
> It worked fine before.
> Subversion pooling log :
> Started on Nov 30, 2011 8:11:31 PM
> Location 'svn+ssh://jenkins@path' does not exist
> One or more repository locations do not exist anymore for hudson.model.FreeStyleProject@3937bf4[], project will be disabled.
> Done. Took 1.3 sec
> No changes

--
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
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[JIRA] (JENKINS-11933) Subversion plugin doesn't probably work correctly with svn server version 1.7.1

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

    [ https://issues.jenkins-ci.org/browse/JENKINS-11933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=156252#comment-156252 ]

Stephane Odul commented on JENKINS-11933:
-----------------------------------------

Hi Kohsuke,

I've been having trouble with this myself and found out that this is an incompatibility bug with SVNKIT which affects other CI tools that rely on SVNKIT.

There will be a fix in SVNKIT 1.7 which is not 'preoduction ready' yet but might be useable for the purpose of this Subversion Plugin.
See: http://svnkit.com/download.php
Here is the explicit warning:
{quote}Subversion 1.7.0 Compatibility
Lastest stable version of SVNKit (1.3.6.1) is not compatible with Subversion 1.7.0 working copy format. However, SVNKit 1.7.0 is under development now and we plan to release it end of November 2011. Before that there will be a preview version available.
Right now you may use SVNKit 1.7.0-SNAPSHOT version, which is available in our maven repository or build SVNKit 1.7.0 from sources. SVNKit 1.7.0-SNAPSHOT is compatible both with the new and old working copy formats, but does not yer support all the Subversion operations.
{quote}

This is the output I get when I try to specify a branch. Note that here the error is different from what Nikita is reporting since in that case it is an 'up' (update) command on an existing client. In my case Jenkins is new and the command is a 'co' (checkout), probably triggering different errors/exceptions in SVNKIT.

{code}
Started by user anonymous
Location 'svn+ssh://svn_host/repo/trunk' does not exist
Checking out a fresh workspace because there's no workspace at /home/jenkins/.jenkins/jobs/Build-trunk-client/workspace
Cleaning local Directory .
Checking out svn+ssh://svn_host/repo/trunk
ERROR: Failed to check out svn+ssh://svn_host/repo/trunk
org.tmatesoft.svn.core.SVNException: svn: URL 'svn+ssh://svn_host/repo/trunk' doesn't exist
        at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64)
        at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51)
        at org.tmatesoft.svn.core.wc.SVNUpdateClient.doCheckout(SVNUpdateClient.java:910)
        at hudson.scm.subversion.CheckoutUpdater$1.perform(CheckoutUpdater.java:84)
        at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:136)
        at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:144)
        at hudson.scm.subversion.UpdateUpdater$TaskImpl.perform(UpdateUpdater.java:120)
        at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:136)
        at hudson.scm.SubversionSCM$CheckOutTask.perform(SubversionSCM.java:787)
        at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:768)
        at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:752)
        at hudson.FilePath.act(FilePath.java:783)
        at hudson.FilePath.act(FilePath.java:765)
        at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:742)
        at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:684)
        at hudson.model.AbstractProject.checkout(AbstractProject.java:1195)
        at hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:568)
        at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:457)
        at hudson.model.Run.run(Run.java:1404)
        at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
        at hudson.model.ResourceController.execute(ResourceController.java:88)
        at hudson.model.Executor.run(Executor.java:238)
Caused by: org.tmatesoft.svn.core.SVNErrorMessage: svn: URL 'svn+ssh://svn_host/repo/trunk' doesn't exist
        at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:163)
        at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:118)
        at org.tmatesoft.svn.core.wc.SVNUpdateClient.doCheckout(SVNUpdateClient.java:909)
        ... 19 more
FATAL: null
java.lang.NullPointerException
        at java.util.ArrayList.addAll(ArrayList.java:497)
        at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:742)
        at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:684)
        at hudson.model.AbstractProject.checkout(AbstractProject.java:1195)
        at hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:568)
        at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:457)
        at hudson.model.Run.run(Run.java:1404)
        at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
        at hudson.model.ResourceController.execute(ResourceController.java:88)
        at hudson.model.Executor.run(Executor.java:238)
{code}

If I use 'svn+ssh://svn_host/repo/' then the Job will happily sync the *entire* repo including /trunk/, /branches/ and /tags/. This is obviously not an option as it would take hours to do a clean sync and we would probably run out of disk space.

I will see with our SVN admin if we can roll back to SVN 1.6 but that is probably not possible.

               

> Subversion plugin doesn't probably work correctly with svn server version 1.7.1
> -------------------------------------------------------------------------------
>
>                 Key: JENKINS-11933
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-11933
>             Project: Jenkins
>          Issue Type: Bug
>          Components: subversion
>    Affects Versions: current
>         Environment: svn server 1.7.1
> ubuntu
>            Reporter: Nikita Aznauryan
>            Priority: Blocker
>
> I use usernames in my svn path like:
> svn+ssh://jenkins@somepath
> but I get a warning "... doesn't exist in the repository"
> I think it started after svn server has been updated to 1.7.1 version
> It worked fine before.
> Subversion pooling log :
> Started on Nov 30, 2011 8:11:31 PM
> Location 'svn+ssh://jenkins@path' does not exist
> One or more repository locations do not exist anymore for hudson.model.FreeStyleProject@3937bf4[], project will be disabled.
> Done. Took 1.3 sec
> No changes

--
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
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[JIRA] (JENKINS-11933) Subversion plugin doesn't probably work correctly with svn server version 1.7.1

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

    [ https://issues.jenkins-ci.org/browse/JENKINS-11933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=156280#comment-156280 ]

Simon Ravenhill commented on JENKINS-11933:
-------------------------------------------

This caught me out too but I found really nasty work around:

Follow the instructions here to build SVNKit from trunk: http://svnkit.com/download.php i.e:

svn co http://svn.svnkit.com/repos/svnkit/trunk/
./gradlew clean build -x test

This should create a jar file called svnkit-1.7.0-SNAPSHOT_v20111203_1635.jar + sqljet-1.1.0-SNAPSHOT_r1158_v20110809_2108.jar, obviously depending on the precise revision when you do the checkout.

Copy both files into your $JENKINS/plugins/subversion/lib directory.

Unzip both the existing and new SVNKit Jar files into temporary directories and then copy 'ISVNAuthenticationOutcomeListener.class' from the old unzipped SVNKit to the new SVNKit temporary directory at the same relative position. Rezip the new SVNKit from within the new temporary directory with 'zip -r ../svnkit-1.7.0-SNAPSHOT_v20111203_1635.jar .'

Delete the old SVN kit jar and any temporary files, move your new botched SVNKit jar into place and restart Jenkins. You should find you can now use svn+ssh against 1.7.1


               

> Subversion plugin doesn't probably work correctly with svn server version 1.7.1
> -------------------------------------------------------------------------------
>
>                 Key: JENKINS-11933
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-11933
>             Project: Jenkins
>          Issue Type: Bug
>          Components: subversion
>    Affects Versions: current
>         Environment: svn server 1.7.1
> ubuntu
>            Reporter: Nikita Aznauryan
>            Priority: Blocker
>              Labels: plugin
>
> I use usernames in my svn path like:
> svn+ssh://jenkins@somepath
> but I get a warning "... doesn't exist in the repository"
> I think it started after svn server has been updated to 1.7.1 version
> It worked fine before.
> Subversion pooling log :
> Started on Nov 30, 2011 8:11:31 PM
> Location 'svn+ssh://jenkins@path' does not exist
> One or more repository locations do not exist anymore for hudson.model.FreeStyleProject@3937bf4[], project will be disabled.
> Done. Took 1.3 sec
> No changes

--
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
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[JIRA] (JENKINS-11933) Subversion plugin doesn't probably work correctly with svn server version 1.7.1

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

    [ https://issues.jenkins-ci.org/browse/JENKINS-11933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=156280#comment-156280 ]

Simon Ravenhill edited comment on JENKINS-11933 at 12/3/11 5:42 PM:
--------------------------------------------------------------------

This caught me out too but I found really nasty work around:

Follow the instructions here to build SVNKit from trunk: http://svnkit.com/download.php i.e:

svn co http://svn.svnkit.com/repos/svnkit/trunk/
./gradlew clean build -x test

This should create a jar file called svnkit-1.7.0-SNAPSHOT_v20111203_1635.jar + sqljet-1.1.0-SNAPSHOT_r1158_v20110809_2108.jar, obviously depending on the precise revision when you do the checkout.

Copy both files into your $JENKINS/plugins/subversion/WEB-INF/lib directory.

Unzip both the existing and new SVNKit Jar files into temporary directories and then copy 'ISVNAuthenticationOutcomeListener.class' from the old unzipped SVNKit to the new SVNKit temporary directory at the same relative position. Rezip the new SVNKit from within the new temporary directory with 'zip -r ../svnkit-1.7.0-SNAPSHOT_v20111203_1635.jar .'

Delete the old SVN kit jar and any temporary files, move your new botched SVNKit jar into place and restart Jenkins. You should find you can now use svn+ssh against 1.7.1


               
      was (Author: simon1983):
    This caught me out too but I found really nasty work around:

Follow the instructions here to build SVNKit from trunk: http://svnkit.com/download.php i.e:

svn co http://svn.svnkit.com/repos/svnkit/trunk/
./gradlew clean build -x test

This should create a jar file called svnkit-1.7.0-SNAPSHOT_v20111203_1635.jar + sqljet-1.1.0-SNAPSHOT_r1158_v20110809_2108.jar, obviously depending on the precise revision when you do the checkout.

Copy both files into your $JENKINS/plugins/subversion/lib directory.

Unzip both the existing and new SVNKit Jar files into temporary directories and then copy 'ISVNAuthenticationOutcomeListener.class' from the old unzipped SVNKit to the new SVNKit temporary directory at the same relative position. Rezip the new SVNKit from within the new temporary directory with 'zip -r ../svnkit-1.7.0-SNAPSHOT_v20111203_1635.jar .'

Delete the old SVN kit jar and any temporary files, move your new botched SVNKit jar into place and restart Jenkins. You should find you can now use svn+ssh against 1.7.1


                 

> Subversion plugin doesn't probably work correctly with svn server version 1.7.1
> -------------------------------------------------------------------------------
>
>                 Key: JENKINS-11933
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-11933
>             Project: Jenkins
>          Issue Type: Bug
>          Components: subversion
>    Affects Versions: current
>         Environment: svn server 1.7.1
> ubuntu
>            Reporter: Nikita Aznauryan
>            Priority: Blocker
>              Labels: plugin
>
> I use usernames in my svn path like:
> svn+ssh://jenkins@somepath
> but I get a warning "... doesn't exist in the repository"
> I think it started after svn server has been updated to 1.7.1 version
> It worked fine before.
> Subversion pooling log :
> Started on Nov 30, 2011 8:11:31 PM
> Location 'svn+ssh://jenkins@path' does not exist
> One or more repository locations do not exist anymore for hudson.model.FreeStyleProject@3937bf4[], project will be disabled.
> Done. Took 1.3 sec
> No changes

--
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
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[JIRA] (JENKINS-11933) Subversion plugin doesn't probably work correctly with svn server version 1.7.1

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

    [ https://issues.jenkins-ci.org/browse/JENKINS-11933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=156281#comment-156281 ]

Simon Ravenhill commented on JENKINS-11933:
-------------------------------------------

Please disregard my previous comment. As you would imagine it has proven unstable and I would not recommend it.
               

> Subversion plugin doesn't probably work correctly with svn server version 1.7.1
> -------------------------------------------------------------------------------
>
>                 Key: JENKINS-11933
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-11933
>             Project: Jenkins
>          Issue Type: Bug
>          Components: subversion
>    Affects Versions: current
>         Environment: svn server 1.7.1
> ubuntu
>            Reporter: Nikita Aznauryan
>            Priority: Blocker
>              Labels: plugin
>
> I use usernames in my svn path like:
> svn+ssh://jenkins@somepath
> but I get a warning "... doesn't exist in the repository"
> I think it started after svn server has been updated to 1.7.1 version
> It worked fine before.
> Subversion pooling log :
> Started on Nov 30, 2011 8:11:31 PM
> Location 'svn+ssh://jenkins@path' does not exist
> One or more repository locations do not exist anymore for hudson.model.FreeStyleProject@3937bf4[], project will be disabled.
> Done. Took 1.3 sec
> No changes

--
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
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[JIRA] (JENKINS-11933) Subversion plugin doesn't probably work correctly with svn server version 1.7.1

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

    [ https://issues.jenkins-ci.org/browse/JENKINS-11933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=156367#comment-156367 ]

Stephane Odul commented on JENKINS-11933:
-----------------------------------------

What I'm doing for the moment is create a read-only git replica of the svn repo and have a Jenkins Job keep it in sync (1m lag). I did not import the entire history of the repo to save time (just last 2 weeks) as it will allow me to get up and running with Jenkins and showcase it as a good replacement for BuildBot. Once SVNKIT and the SVN Plugin are fixed switching back to svn for Jenkins should be trivial.

I do not recommend to do that to build your Prod builds if you plan on sticking with SVN, better roll back to SVN 1.6 if you can. For my purposes (continuous feedback on the submitted code) this will do for a few weeks. It will probably not scale on large repos (200k+) or repos with very large files due to git limitations.

An other options could be for you to stand up a SVN 1.6 read-only replica of your 1.7 master.
               

> Subversion plugin doesn't probably work correctly with svn server version 1.7.1
> -------------------------------------------------------------------------------
>
>                 Key: JENKINS-11933
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-11933
>             Project: Jenkins
>          Issue Type: Bug
>          Components: subversion
>    Affects Versions: current
>         Environment: svn server 1.7.1
> ubuntu
>            Reporter: Nikita Aznauryan
>            Priority: Blocker
>              Labels: plugin
>
> I use usernames in my svn path like:
> svn+ssh://jenkins@somepath
> but I get a warning "... doesn't exist in the repository"
> I think it started after svn server has been updated to 1.7.1 version
> It worked fine before.
> Subversion pooling log :
> Started on Nov 30, 2011 8:11:31 PM
> Location 'svn+ssh://jenkins@path' does not exist
> One or more repository locations do not exist anymore for hudson.model.FreeStyleProject@3937bf4[], project will be disabled.
> Done. Took 1.3 sec
> No changes

--
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
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[JIRA] (JENKINS-11933) Subversion plugin doesn't probably work correctly with svn server version 1.7.1

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

    [ https://issues.jenkins-ci.org/browse/JENKINS-11933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=156382#comment-156382 ]

erben22 commented on JENKINS-11933:
-----------------------------------

This issue is covered in [SVNKIT-153|http://issues.tmatesoft.com/issue/SVNKIT-153], which is noted to be fixed in an upcoming 1.3.7 release.  The [svn-dev discussion|http://article.gmane.org/gmane.comp.version-control.subversion.devel/132476] referenced covers the details, but in summary, this issue affects any paths below the root due to how SVNKit used absolute paths instead of relative paths, and tightening up of the API in Subversion 1.7.x.

For me, I was able to downgrade to 1.6.x to work-around this issue for now.
               

> Subversion plugin doesn't probably work correctly with svn server version 1.7.1
> -------------------------------------------------------------------------------
>
>                 Key: JENKINS-11933
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-11933
>             Project: Jenkins
>          Issue Type: Bug
>          Components: subversion
>    Affects Versions: current
>         Environment: svn server 1.7.1
> ubuntu
>            Reporter: Nikita Aznauryan
>            Priority: Blocker
>              Labels: plugin
>
> I use usernames in my svn path like:
> svn+ssh://jenkins@somepath
> but I get a warning "... doesn't exist in the repository"
> I think it started after svn server has been updated to 1.7.1 version
> It worked fine before.
> Subversion pooling log :
> Started on Nov 30, 2011 8:11:31 PM
> Location 'svn+ssh://jenkins@path' does not exist
> One or more repository locations do not exist anymore for hudson.model.FreeStyleProject@3937bf4[], project will be disabled.
> Done. Took 1.3 sec
> No changes

--
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
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[JIRA] (JENKINS-11933) Subversion plugin doesn't probably work correctly with svn server version 1.7.1

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

    [ https://issues.jenkins-ci.org/browse/JENKINS-11933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=156492#comment-156492 ]

Stephane Odul commented on JENKINS-11933:
-----------------------------------------

Apparently 1.3.7 which was released on Dec 6 should work now:
{quote}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.
{quote}

               

> Subversion plugin doesn't probably work correctly with svn server version 1.7.1
> -------------------------------------------------------------------------------
>
>                 Key: JENKINS-11933
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-11933
>             Project: Jenkins
>          Issue Type: Bug
>          Components: subversion
>    Affects Versions: current
>         Environment: svn server 1.7.1
> ubuntu
>            Reporter: Nikita Aznauryan
>            Priority: Blocker
>              Labels: plugin
>
> I use usernames in my svn path like:
> svn+ssh://jenkins@somepath
> but I get a warning "... doesn't exist in the repository"
> I think it started after svn server has been updated to 1.7.1 version
> It worked fine before.
> Subversion pooling log :
> Started on Nov 30, 2011 8:11:31 PM
> Location 'svn+ssh://jenkins@path' does not exist
> One or more repository locations do not exist anymore for hudson.model.FreeStyleProject@3937bf4[], project will be disabled.
> Done. Took 1.3 sec
> No changes

--
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
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[JIRA] (JENKINS-11933) Subversion plugin doesn't probably work correctly with svn server version 1.7.1

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

    [ https://issues.jenkins-ci.org/browse/JENKINS-11933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=156608#comment-156608 ]

David Carson commented on JENKINS-11933:
----------------------------------------

So, now that SVNKit 1.3.7 has fixed the path issue for svn 1.7 servers, should we be expecting a new version of the SVN plugin, which incorporates this fix?  I am stuck with svn 1.7 servers, but would really like to use the svn plugin.  Currently, it cannot check out the code because the URL is formed wrong.
               

> Subversion plugin doesn't probably work correctly with svn server version 1.7.1
> -------------------------------------------------------------------------------
>
>                 Key: JENKINS-11933
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-11933
>             Project: Jenkins
>          Issue Type: Bug
>          Components: subversion
>    Affects Versions: current
>         Environment: svn server 1.7.1
> ubuntu
>            Reporter: Nikita Aznauryan
>            Priority: Blocker
>              Labels: plugin
>
> I use usernames in my svn path like:
> svn+ssh://jenkins@somepath
> but I get a warning "... doesn't exist in the repository"
> I think it started after svn server has been updated to 1.7.1 version
> It worked fine before.
> Subversion pooling log :
> Started on Nov 30, 2011 8:11:31 PM
> Location 'svn+ssh://jenkins@path' does not exist
> One or more repository locations do not exist anymore for hudson.model.FreeStyleProject@3937bf4[], project will be disabled.
> Done. Took 1.3 sec
> No changes

--
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
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[JIRA] (JENKINS-11933) Subversion plugin doesn't probably work correctly with svn server version 1.7.1

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

    [ https://issues.jenkins-ci.org/browse/JENKINS-11933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=156609#comment-156609 ]

rombert commented on JENKINS-11933:
-----------------------------------

As suggested on the mailing list, you should be able to expose your repository over http(s) and use that for Jenkins.
               

> Subversion plugin doesn't probably work correctly with svn server version 1.7.1
> -------------------------------------------------------------------------------
>
>                 Key: JENKINS-11933
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-11933
>             Project: Jenkins
>          Issue Type: Bug
>          Components: subversion
>    Affects Versions: current
>         Environment: svn server 1.7.1
> ubuntu
>            Reporter: Nikita Aznauryan
>            Priority: Blocker
>              Labels: plugin
>
> I use usernames in my svn path like:
> svn+ssh://jenkins@somepath
> but I get a warning "... doesn't exist in the repository"
> I think it started after svn server has been updated to 1.7.1 version
> It worked fine before.
> Subversion pooling log :
> Started on Nov 30, 2011 8:11:31 PM
> Location 'svn+ssh://jenkins@path' does not exist
> One or more repository locations do not exist anymore for hudson.model.FreeStyleProject@3937bf4[], project will be disabled.
> Done. Took 1.3 sec
> No changes

--
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
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[JIRA] (JENKINS-11933) Subversion plugin doesn't probably work correctly with svn server version 1.7.1

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

    [ https://issues.jenkins-ci.org/browse/JENKINS-11933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=157652#comment-157652 ]

David Carson commented on JENKINS-11933:
----------------------------------------

Thanks for the suggestion to use http protocol as a workaround for the svn protocol problem using SVNKit with svn 1.7 server.

Unfortunately, it does not work either.  I am now hitting this error instead:
  http://old.nabble.com/REPORT-request-failed-accessing-Sourceforge-Subversion-td14733189.html

So, I either have to fix the SVNKit issue with the http protocol, the issue with the svn protocol, or just not use svn 1.7 on my server.  I need fixes in svn 1.7, so I don't want to abandon my effort to get this working.

Since I have no idea when a new version of Jenkins will come out that uses the new SVNKit (with fix), I would like to try using the current Jenkins and replacing SVNKit myself.  Any advice on how to do this would be appreciated.  (I also have to do the same thing for a Hudson installation, making it even less likely that I just want to wait for Jenkins/Hudson to come out with a version that includes the fixes SVNKit.)
               

> Subversion plugin doesn't probably work correctly with svn server version 1.7.1
> -------------------------------------------------------------------------------
>
>                 Key: JENKINS-11933
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-11933
>             Project: Jenkins
>          Issue Type: Bug
>          Components: subversion
>    Affects Versions: current
>         Environment: svn server 1.7.1
> ubuntu
>            Reporter: Nikita Aznauryan
>            Priority: Blocker
>              Labels: plugin
>
> I use usernames in my svn path like:
> svn+ssh://jenkins@somepath
> but I get a warning "... doesn't exist in the repository"
> I think it started after svn server has been updated to 1.7.1 version
> It worked fine before.
> Subversion pooling log :
> Started on Nov 30, 2011 8:11:31 PM
> Location 'svn+ssh://jenkins@path' does not exist
> One or more repository locations do not exist anymore for hudson.model.FreeStyleProject@3937bf4[], project will be disabled.
> Done. Took 1.3 sec
> No changes

--
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
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[JIRA] (JENKINS-11933) Subversion plugin doesn't probably work correctly with svn server version 1.7.1

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

     [ https://issues.jenkins-ci.org/browse/JENKINS-11933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

centic updated JENKINS-11933:
-----------------------------

    Attachment: 0001-imported-1.3.7.patch
                0002-Adjust-version-number-in-pom.patch
                0003-update-version-and-add-second-maven-repository-to-ge.patch

Here my patches which up-port the changes in the svnkit-git-repository to 1.3.7.

The last patch may not be needed, for some reason i could not get the sqljet dependency otherwise.

I can provide this as git-repository as well if somebody is interested.

The resulting svnkit-library can then be included in the subversion-plugin to allow to access 1.7 subversion servers with the ssh+svn-protocol.

I will post the necessary changes to the subversion plugin in a minute...
               

> Subversion plugin doesn't probably work correctly with svn server version 1.7.1
> -------------------------------------------------------------------------------
>
>                 Key: JENKINS-11933
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-11933
>             Project: Jenkins
>          Issue Type: Bug
>          Components: subversion
>    Affects Versions: current
>         Environment: svn server 1.7.1
> ubuntu
>            Reporter: Nikita Aznauryan
>            Priority: Blocker
>              Labels: plugin
>         Attachments: 0001-imported-1.3.7.patch, 0002-Adjust-version-number-in-pom.patch, 0003-update-version-and-add-second-maven-repository-to-ge.patch
>
>
> I use usernames in my svn path like:
> svn+ssh://jenkins@somepath
> but I get a warning "... doesn't exist in the repository"
> I think it started after svn server has been updated to 1.7.1 version
> It worked fine before.
> Subversion pooling log :
> Started on Nov 30, 2011 8:11:31 PM
> Location 'svn+ssh://jenkins@path' does not exist
> One or more repository locations do not exist anymore for hudson.model.FreeStyleProject@3937bf4[], project will be disabled.
> Done. Took 1.3 sec
> No changes

--
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
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[JIRA] (JENKINS-11933) Subversion plugin doesn't probably work correctly with svn server version 1.7.1

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

     [ https://issues.jenkins-ci.org/browse/JENKINS-11933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

centic updated JENKINS-11933:
-----------------------------

    Attachment: 0005_subversion_plugin_svnkit_1_3_7.patch

Patch for subversion-plugin to build locally with the updated svnkit-library, I am not sure if any of these is actually needed or if these are just local problems that need to be worked around.
               

> Subversion plugin doesn't probably work correctly with svn server version 1.7.1
> -------------------------------------------------------------------------------
>
>                 Key: JENKINS-11933
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-11933
>             Project: Jenkins
>          Issue Type: Bug
>          Components: subversion
>    Affects Versions: current
>         Environment: svn server 1.7.1
> ubuntu
>            Reporter: Nikita Aznauryan
>            Priority: Blocker
>              Labels: plugin
>         Attachments: 0001-imported-1.3.7.patch, 0002-Adjust-version-number-in-pom.patch, 0003-update-version-and-add-second-maven-repository-to-ge.patch, 0005_subversion_plugin_svnkit_1_3_7.patch
>
>
> I use usernames in my svn path like:
> svn+ssh://jenkins@somepath
> but I get a warning "... doesn't exist in the repository"
> I think it started after svn server has been updated to 1.7.1 version
> It worked fine before.
> Subversion pooling log :
> Started on Nov 30, 2011 8:11:31 PM
> Location 'svn+ssh://jenkins@path' does not exist
> One or more repository locations do not exist anymore for hudson.model.FreeStyleProject@3937bf4[], project will be disabled.
> Done. Took 1.3 sec
> No changes

--
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
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[JIRA] (JENKINS-11933) Subversion plugin doesn't probably work correctly with svn server version 1.7.1

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

    [ https://issues.jenkins-ci.org/browse/JENKINS-11933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=157652#comment-157652 ]

David Carson edited comment on JENKINS-11933 at 1/11/12 8:04 PM:
-----------------------------------------------------------------

Thanks for the suggestion to use http protocol as a workaround for the svn protocol problem using SVNKit with svn 1.7 server.

Unfortunately, it does not work either.  I am now hitting this error instead:
  http://old.nabble.com/REPORT-request-failed-accessing-Sourceforge-Subversion-td14733189.html

So, I either have to fix the SVNKit issue with the http protocol, the issue with the svn protocol, or just not use svn 1.7 on my server.  I need fixes in svn 1.7, so I don't want to abandon my effort to get this working.

Since I have no idea when a new version of Jenkins will come out that uses the new SVNKit (with fix), I would like to try using the current Jenkins and replacing SVNKit myself.  Any advice on how to do this would be appreciated.  (I also have to do the same thing for a Hudson installation, making it even less likely that I just want to wait for Jenkins/Hudson to come out with a version that includes the fixed SVNKit.)
               
      was (Author: dccarson):
    Thanks for the suggestion to use http protocol as a workaround for the svn protocol problem using SVNKit with svn 1.7 server.

Unfortunately, it does not work either.  I am now hitting this error instead:
  http://old.nabble.com/REPORT-request-failed-accessing-Sourceforge-Subversion-td14733189.html

So, I either have to fix the SVNKit issue with the http protocol, the issue with the svn protocol, or just not use svn 1.7 on my server.  I need fixes in svn 1.7, so I don't want to abandon my effort to get this working.

Since I have no idea when a new version of Jenkins will come out that uses the new SVNKit (with fix), I would like to try using the current Jenkins and replacing SVNKit myself.  Any advice on how to do this would be appreciated.  (I also have to do the same thing for a Hudson installation, making it even less likely that I just want to wait for Jenkins/Hudson to come out with a version that includes the fixes SVNKit.)
                 

> Subversion plugin doesn't probably work correctly with svn server version 1.7.1
> -------------------------------------------------------------------------------
>
>                 Key: JENKINS-11933
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-11933
>             Project: Jenkins
>          Issue Type: Bug
>          Components: subversion
>    Affects Versions: current
>         Environment: svn server 1.7.1
> ubuntu
>            Reporter: Nikita Aznauryan
>            Priority: Blocker
>              Labels: plugin
>         Attachments: 0001-imported-1.3.7.patch, 0002-Adjust-version-number-in-pom.patch, 0003-update-version-and-add-second-maven-repository-to-ge.patch, 0005_subversion_plugin_svnkit_1_3_7.patch
>
>
> I use usernames in my svn path like:
> svn+ssh://jenkins@somepath
> but I get a warning "... doesn't exist in the repository"
> I think it started after svn server has been updated to 1.7.1 version
> It worked fine before.
> Subversion pooling log :
> Started on Nov 30, 2011 8:11:31 PM
> Location 'svn+ssh://jenkins@path' does not exist
> One or more repository locations do not exist anymore for hudson.model.FreeStyleProject@3937bf4[], project will be disabled.
> Done. Took 1.3 sec
> No changes

--
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
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[JIRA] (JENKINS-11933) Subversion plugin doesn't probably work correctly with svn server version 1.7.1

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

    [ https://issues.jenkins-ci.org/browse/JENKINS-11933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159324#comment-159324 ]

Luke Last commented on JENKINS-11933:
-------------------------------------

Can someone please update to SVNKIT 1.3.7? This is preventing us from upgrading our server to Subversion 1.7
               

> Subversion plugin doesn't probably work correctly with svn server version 1.7.1
> -------------------------------------------------------------------------------
>
>                 Key: JENKINS-11933
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-11933
>             Project: Jenkins
>          Issue Type: Bug
>          Components: subversion
>    Affects Versions: current
>         Environment: svn server 1.7.1
> ubuntu
>            Reporter: Nikita Aznauryan
>            Priority: Blocker
>              Labels: plugin
>         Attachments: 0001-imported-1.3.7.patch, 0002-Adjust-version-number-in-pom.patch, 0003-update-version-and-add-second-maven-repository-to-ge.patch, 0005_subversion_plugin_svnkit_1_3_7.patch
>
>
> I use usernames in my svn path like:
> svn+ssh://jenkins@somepath
> but I get a warning "... doesn't exist in the repository"
> I think it started after svn server has been updated to 1.7.1 version
> It worked fine before.
> Subversion pooling log :
> Started on Nov 30, 2011 8:11:31 PM
> Location 'svn+ssh://jenkins@path' does not exist
> One or more repository locations do not exist anymore for hudson.model.FreeStyleProject@3937bf4[], project will be disabled.
> Done. Took 1.3 sec
> No changes

--
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
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[JIRA] (JENKINS-11933) Subversion plugin doesn't probably work correctly with svn server version 1.7.1

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

     [ https://issues.jenkins-ci.org/browse/JENKINS-11933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

hyunsoo lee reassigned JENKINS-11933:
-------------------------------------

    Assignee: hyunsoo lee
   

> Subversion plugin doesn't probably work correctly with svn server version 1.7.1
> -------------------------------------------------------------------------------
>
>                 Key: JENKINS-11933
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-11933
>             Project: Jenkins
>          Issue Type: Bug
>          Components: subversion
>    Affects Versions: current
>         Environment: svn server 1.7.1
> ubuntu
>            Reporter: Nikita Aznauryan
>            Assignee: hyunsoo lee
>            Priority: Blocker
>              Labels: plugin
>         Attachments: 0001-imported-1.3.7.patch, 0002-Adjust-version-number-in-pom.patch, 0003-update-version-and-add-second-maven-repository-to-ge.patch, 0005_subversion_plugin_svnkit_1_3_7.patch
>
>
> I use usernames in my svn path like:
> svn+ssh://jenkins@somepath
> but I get a warning "... doesn't exist in the repository"
> I think it started after svn server has been updated to 1.7.1 version
> It worked fine before.
> Subversion pooling log :
> Started on Nov 30, 2011 8:11:31 PM
> Location 'svn+ssh://jenkins@path' does not exist
> One or more repository locations do not exist anymore for hudson.model.FreeStyleProject@3937bf4[], project will be disabled.
> Done. Took 1.3 sec
> No changes

--
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
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[JIRA] (JENKINS-11933) Subversion plugin doesn't probably work correctly with svn server version 1.7.1

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

     [ https://issues.jenkins-ci.org/browse/JENKINS-11933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

hyunsoo lee updated JENKINS-11933:
----------------------------------

    Assignee:     (was: hyunsoo lee)

my mistake :(
               

> Subversion plugin doesn't probably work correctly with svn server version 1.7.1
> -------------------------------------------------------------------------------
>
>                 Key: JENKINS-11933
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-11933
>             Project: Jenkins
>          Issue Type: Bug
>          Components: subversion
>    Affects Versions: current
>         Environment: svn server 1.7.1
> ubuntu
>            Reporter: Nikita Aznauryan
>            Priority: Blocker
>              Labels: plugin
>         Attachments: 0001-imported-1.3.7.patch, 0002-Adjust-version-number-in-pom.patch, 0003-update-version-and-add-second-maven-repository-to-ge.patch, 0005_subversion_plugin_svnkit_1_3_7.patch
>
>
> I use usernames in my svn path like:
> svn+ssh://jenkins@somepath
> but I get a warning "... doesn't exist in the repository"
> I think it started after svn server has been updated to 1.7.1 version
> It worked fine before.
> Subversion pooling log :
> Started on Nov 30, 2011 8:11:31 PM
> Location 'svn+ssh://jenkins@path' does not exist
> One or more repository locations do not exist anymore for hudson.model.FreeStyleProject@3937bf4[], project will be disabled.
> Done. Took 1.3 sec
> No changes

--
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
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[JIRA] (JENKINS-11933) Subversion plugin doesn't probably work correctly with svn server version 1.7.1

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

    [ https://issues.jenkins-ci.org/browse/JENKINS-11933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160509#comment-160509 ]

Aaron Laws commented on JENKINS-11933:
--------------------------------------

This is a duplicate of 11381 , right?
               

> Subversion plugin doesn't probably work correctly with svn server version 1.7.1
> -------------------------------------------------------------------------------
>
>                 Key: JENKINS-11933
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-11933
>             Project: Jenkins
>          Issue Type: Bug
>          Components: subversion
>    Affects Versions: current
>         Environment: svn server 1.7.1
> ubuntu
>            Reporter: Nikita Aznauryan
>            Priority: Blocker
>              Labels: plugin
>         Attachments: 0001-imported-1.3.7.patch, 0002-Adjust-version-number-in-pom.patch, 0003-update-version-and-add-second-maven-repository-to-ge.patch, 0005_subversion_plugin_svnkit_1_3_7.patch
>
>
> I use usernames in my svn path like:
> svn+ssh://jenkins@somepath
> but I get a warning "... doesn't exist in the repository"
> I think it started after svn server has been updated to 1.7.1 version
> It worked fine before.
> Subversion pooling log :
> Started on Nov 30, 2011 8:11:31 PM
> Location 'svn+ssh://jenkins@path' does not exist
> One or more repository locations do not exist anymore for hudson.model.FreeStyleProject@3937bf4[], project will be disabled.
> Done. Took 1.3 sec
> No changes

--
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
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[JIRA] (JENKINS-11933) Subversion plugin doesn't probably work correctly with svn server version 1.7.1

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

    [ https://issues.jenkins-ci.org/browse/JENKINS-11933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160509#comment-160509 ]

Aaron Laws edited comment on JENKINS-11933 at 3/20/12 10:02 PM:
----------------------------------------------------------------

This is a duplicate of 11381 , right?
Oh, I guess that's a duplicate of this... /scratches head

This is preventing me from using Jenkins so the Blocker priority is right on!

I would just roll back to svn 1.6, but I have other services (python bindings involved...) that depend on 1.7.  Fix it please.  I'd be glad to fix it with a little help.
               
      was (Author: limited_atonement):
    This is a duplicate of 11381 , right?
                 

> Subversion plugin doesn't probably work correctly with svn server version 1.7.1
> -------------------------------------------------------------------------------
>
>                 Key: JENKINS-11933
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-11933
>             Project: Jenkins
>          Issue Type: Bug
>          Components: subversion
>    Affects Versions: current
>         Environment: svn server 1.7.1
> ubuntu
>            Reporter: Nikita Aznauryan
>            Priority: Blocker
>              Labels: plugin
>         Attachments: 0001-imported-1.3.7.patch, 0002-Adjust-version-number-in-pom.patch, 0003-update-version-and-add-second-maven-repository-to-ge.patch, 0005_subversion_plugin_svnkit_1_3_7.patch
>
>
> I use usernames in my svn path like:
> svn+ssh://jenkins@somepath
> but I get a warning "... doesn't exist in the repository"
> I think it started after svn server has been updated to 1.7.1 version
> It worked fine before.
> Subversion pooling log :
> Started on Nov 30, 2011 8:11:31 PM
> Location 'svn+ssh://jenkins@path' does not exist
> One or more repository locations do not exist anymore for hudson.model.FreeStyleProject@3937bf4[], project will be disabled.
> Done. Took 1.3 sec
> No changes

--
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
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
12
Loading...