[JIRA] (JENKINS-13835) upgrading Subversion Plugin to 1.40 totally ruined our CI server
pancake@java.net (JIRA)
---------------------------------
Summary: upgrading Subversion Plugin to 1.40 totally ruined our CI server
Key: JENKINS-13835
URL: https://issues.jenkins-ci.org/browse/JENKINS-13835
Project: Jenkins
Issue Type: Bug
Components: subversion
Environment: Jenkins ver. 1.460; Subversion Plugin 1.40, 1.39; Windows Server 2003 R2 x64 SP2
Reporter: pancake
Priority: Blocker
Updating Subversion Plugin to 1.40 caused multiple bugs. Rolling back to 1.39 resulted to {color:red}complete inability to perform a checkout. CI server is totally unusable now.{color}
*Issue #1*
After updating to Subversion Plugin to 1.40 (from 1.39) this exception started occurring _sometimes_ (various salves, various jobs):
{quote}
Checking out a fresh workspace because there's no workspace at C:\_JenkinsCI\workspace\XXX
Cleaning local Directory .
Checking out http://oursvnserver/svn/svnLatest/.../XXX
A ...
ERROR: Failed to check out http://oursvnserver/svn/svnLatest/.../XXX
org.tmatesoft.svn.core.SVNException: svn: E175002: REPORT /svn/svnLatest/!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.wc2.ng.SvnNgAbstractUpdate.updateInternal(SvnNgAbstractUpdate.java:216)
at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgAbstractUpdate.update(SvnNgAbstractUpdate.java:100)
at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgAbstractUpdate.checkout(SvnNgAbstractUpdate.java:756)
at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgCheckout.run(SvnNgCheckout.java:14)
at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgCheckout.run(SvnNgCheckout.java:9)
at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgOperationRunner.run(SvnNgOperationRunner.java:20)
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:85)
at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:144)
at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:152)
at hudson.scm.subversion.UpdateUpdater$TaskImpl.perform(UpdateUpdater.java:121)
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$FileCallableWrapper.call(FilePath.java:2154)
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(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Caused by: svn: E175002: REPORT /svn/svnLatest/!svn/vcc/default failed
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)
... 35 more
FATAL: null
java.lang.NullPointerException
{quote}
*Issue #2*
{{Emulate clean checkout by first deleting unversioned/ignored files, then 'svn update'}} no longer deletes unversioned files in 1.40.
*Issue #3*
Because of #2 and #3 I've decided to roll back to 1.39. So, I've wiped out all workspaces on all nodes and... 1.39 is no longer able to checkout due to:
{quote}
Checking out a fresh workspace because there's no workspace at C:\_JenkinsCI\workspace\update_Tools_on_all_nodes
Cleaning local Directory .
Checking out http://oursvnserver/svn/svnLatest/Tools
ERROR: Failed to check out http://oursvnserver/svn/svnLatest/Tools
org.tmatesoft.svn.core.SVNException: svn: 'C:\_JenkinsCI\workspace\update_Tools_on_all_nodes' 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:197)
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.wc.SVNUpdateClient.update(SVNUpdateClient.java:512)
at org.tmatesoft.svn.core.wc.SVNUpdateClient.doCheckout(SVNUpdateClient.java:942)
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:121)
at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:136)
at hudson.scm.SubversionSCM$CheckOutTask.perform(SubversionSCM.java:788)
at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:769)
at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:753)
at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2154)
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(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Caused by: org.tmatesoft.svn.core.SVNErrorMessage: svn: 'C:\_JenkinsCI\workspace\update_Tools_on_all_nodes' is not a working copy
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.internal.wc.admin.SVNAdminAreaFactory.open(SVNAdminAreaFactory.java:192)
... 24 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:1421)
at hudson.matrix.MatrixBuild.run(MatrixBuild.java:248)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:238)
at hudson.model.OneOffExecutor.run(OneOffExecutor.java:66)
{quote}
Needless to say that 'C:\_JenkinsCI\workspace\update_Tools_on_all_nodes' didn't even exist before checkout.
This happens on both slave and master.
--
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
pancake@java.net (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-13835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
pancake updated JENKINS-13835:
------------------------------
Environment: Jenkins ver. 1.460; Subversion Plugin ver. 1.40, 1.39; Windows Server 2003 R2 x64 SP2; Subversion server ver. 1.6.16. (was: Jenkins ver. 1.460; Subversion Plugin 1.40, 1.39; Windows Server 2003 R2 x64 SP2)
> upgrading Subversion Plugin to 1.40 totally ruined our CI server
> Key: JENKINS-13835
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13835
> Project: Jenkins
> Issue Type: Bug
> Components: subversion
> Reporter: pancake
> Priority: Blocker
> Labels: plugin, subversion, windows
pancake@java.net (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-13835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
pancake updated JENKINS-13835:
------------------------------
Found workaround for *Issue #3*: set svn wc format to 1.6 in Jenkins configuration.
After downgrading Subversion Plugin value "1.4" was shown for svn wc format on Jenkins configuration page.
Note I've set it to 1.7 after uprading to Subversion Plugin ver. 1.40.
I.e. either actual value "1.7" of wc format was rendered (and treated) incorrectly or Subversion Plugin ver. 1.39 can't work with wc format 1.4.
I'm now decreasing issue priority to "blocker" \-> "major" since our CI server can function properly due to the workaround. The issues *#1* and *#2* still prevent us from upgrading to Subversion Plugin ver. 1.40.
> upgrading Subversion Plugin to 1.40 totally ruined our CI server
> Key: JENKINS-13835
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13835
> Project: Jenkins
> Issue Type: Bug
> Components: subversion
> Reporter: pancake
aristedes@java.net (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-13835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163307#comment-163307 ]
aristedes commented on JENKINS-13835:
-------------------------------------
I can report a very similar issue. The Subversion 1.7.4 server. 1.40 svn jenkins plugin. Pre-existing 1.6 workspace, and Jenkins set to use a 1.7 checkout format. The problem goes away if you choose 1.6 as the workspace format.
{code}
ERROR: Failed to update https://acme.com/ish/angel/trunk
org.tmatesoft.svn.core.SVNException: svn: E175002: REPORT /ish/!svn/vcc/default failed
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.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.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:144)
at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:770)
at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:753)
at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2154)
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(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
Caused by: svn: E175002: REPORT /ish/!svn/vcc/default failed
at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:154)
at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:97)
{code}
Looks like it tries to upgrade the workspace and fails.
> upgrading Subversion Plugin to 1.40 totally ruined our CI server
> Key: JENKINS-13835
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13835
> Project: Jenkins
> Issue Type: Bug
> Components: subversion
> Reporter: pancake
> Labels: plugin, subversion, windows
>
julien.nicoulaud@gmail.com (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-13835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163470#comment-163470 ]
Julien Nicoulaud commented on JENKINS-13835:
--------------------------------------------
Same here with existing repositories in 1.5 format.
> upgrading Subversion Plugin to 1.40 totally ruined our CI server
> Key: JENKINS-13835
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13835
> Project: Jenkins
> Issue Type: Bug
> Components: subversion
> Reporter: pancake
> Labels: plugin, subversion, windows
>
stephenconnolly@java.net (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-13835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163540#comment-163540 ]
stephenconnolly commented on JENKINS-13835:
-------------------------------------------
This looks to be an encoding issue with your log messages on your subversion server.
Log messages have always been required to be UTF-8. Only recent releases of Subversion started enforcing it better at all layers. The SVN command line client always handled this, but the lower level API's (and I suspect the SVNKit library that Jenkins uses) did not so if you used a different client (i.e. committing from TortoiseSVN or eclipse, etc) it was possible to get non-UTF-8 data into the repository.
You can use svnsync from SVN 1.7 to synch the existing repository to a new repository using the --source-prop-encoding ARG option. This will convert the existing revprops from the specified encoding to UTF-8 as part of synching to a new repository. When the process is done, you can switch in the new repository for the old one to fix your repository.
> upgrading Subversion Plugin to 1.40 totally ruined our CI server
> Key: JENKINS-13835
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13835
> Project: Jenkins
> Issue Type: Bug
> Components: subversion
> Reporter: pancake
> Labels: plugin, subversion, windows
>
luca.orlandi@gmail.com (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-13835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163564#comment-163564 ]
Luca Orlandi commented on JENKINS-13835:
----------------------------------------
Same issue here.
I've also downgraded to jenins 1.464 and subversion plugin 1.34 with NO SUCCESS at all.
I cannot upgrade the server format as suggested in @stephenconnolly comment because of a very large 1.6 repository
It's urgent for me to find a robust workaround (maybe something on apache encoding?).
> upgrading Subversion Plugin to 1.40 totally ruined our CI server
> Key: JENKINS-13835
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13835
> Project: Jenkins
> Issue Type: Bug
> Components: subversion
> Reporter: pancake
> Labels: plugin, subversion, windows
>
luca.orlandi@gmail.com (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-13835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163564#comment-163564 ]
Luca Orlandi edited comment on JENKINS-13835 at 6/6/12 5:51 PM:
----------------------------------------------------------------
Same issue here.
I've also downgraded to jenkins 1.464 and subversion plugin 1.34 with NO SUCCESS at all.
I cannot upgrade the server format as suggested by @stephenconnolly comment because of a very large 1.6 repository
It's urgent for me to find a robust workaround (maybe something on apache encoding?).
Same issue here.
I've also downgraded to jenkins 1.464 and subversion plugin 1.34 with NO SUCCESS at all.
It's urgent for me to find a robust workaround (maybe something on apache encoding?).
> Key: JENKINS-13835
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13835
> Project: Jenkins
> Issue Type: Bug
> Components: subversion
> Reporter: pancake
> Labels: plugin, subversion, windows
>
luca.orlandi@gmail.com (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-13835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163564#comment-163564 ]
Luca Orlandi edited comment on JENKINS-13835 at 6/6/12 5:50 PM:
Same issue here.
I've also downgraded to jenkins 1.464 and subversion plugin 1.34 with NO SUCCESS at all.
It's urgent for me to find a robust workaround (maybe something on apache encoding?).
Same issue here.
It's urgent for me to find a robust workaround (maybe something on apache encoding?).
> Key: JENKINS-13835
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13835
> Project: Jenkins
> Issue Type: Bug
> Components: subversion
> Reporter: pancake
> Labels: plugin, subversion, windows
>
luca.orlandi@gmail.com (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-13835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Luca Orlandi updated JENKINS-13835:
-----------------------------------
Labels: linux plugin subversion windows (was: plugin subversion windows)
> upgrading Subversion Plugin to 1.40 totally ruined our CI server
> Key: JENKINS-13835
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13835
> Project: Jenkins
> Issue Type: Bug
> Components: subversion
> Reporter: pancake
pancake@java.net (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-13835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163593#comment-163593 ]
pancake commented on JENKINS-13835:
-----------------------------------
*stephenconnolly*, E175002 doesn't seem to be related to server encoding issue. The bug occurred totally sporadically, i.e. didn't always reproduce for the same job (hence the same repo URL). In case that was caused by something wrong with repository, it should have been always reproducible for the same URL, right?
*Luca*, there is a workaround for "not a working copy" issue: go to Jenkins configuration and change WC format to 1.6. And E175002 never reproduced for me after downgrading 1.40 -> 1.39.
> upgrading Subversion Plugin to 1.40 totally ruined our CI server
> Key: JENKINS-13835
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13835
> Project: Jenkins
> Issue Type: Bug
> Components: subversion
> Reporter: pancake
> Labels: linux, plugin, subversion, windows
>
marcel@mcbeister.de (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-13835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163654#comment-163654 ]
Marcel Beister commented on JENKINS-13835:
------------------------------------------
I must admit that I'm currently a bit pissed about the 1.40 release of the subversion plugin.
This version introduced several severe issues (emulate cleanup not working, svn-externals not working properly) which should have been detected before the release! But that's not my point... I'm really disappointed on how these problems are dealt with (or NOT dealt with!) after the buggy version has been release. Since 3 weeks nothing has happened and the buggy version is still delivered to all jenkins users!
:-(
> upgrading Subversion Plugin to 1.40 totally ruined our CI server
> Key: JENKINS-13835
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13835
> Project: Jenkins
> Issue Type: Bug
> Components: subversion
> Reporter: pancake
> Labels: linux, plugin, subversion, windows
>
aristedes@java.net (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-13835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163683#comment-163683 ]
aristedes commented on JENKINS-13835:
-------------------------------------
Given the trouble that svnkit has been (bugs, slow update cycle), is there any possibility that this plugin could use the command line svn binary just like the git jenkins plugin does? Yes, I know that is slightly more work for users who then need to ensure it is installed and the path correct, but vastly less work for the developers of the plugin to keep up with.
> upgrading Subversion Plugin to 1.40 totally ruined our CI server
> Key: JENKINS-13835
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13835
> Project: Jenkins
> Issue Type: Bug
> Components: subversion
> Reporter: pancake
> Labels: linux, plugin, subversion, windows
>
aristedes@java.net (JIRA)
[ https://issues.jenkins-ci.org/browse/JENKINS-13835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163683#comment-163683 ]
aristedes edited comment on JENKINS-13835 at 6/9/12 1:01 AM:
-------------------------------------------------------------
@stephenconnolly I don't know if you are right about your hunch that encoding is the source of all these issues. I've been able to upgrade the Jenkins workspace using the command line svn tool without any trouble.
Given the trouble that svnkit has been (bugs, slow update cycle), is there any possibility that this plugin could use the command line svn binary just like the git jenkins plugin does? Yes, I know that is slightly more work for users who then need to ensure it is installed and the path correct, but vastly less work for the developers of the plugin to keep up with.
Given the trouble that svnkit has been (bugs, slow update cycle), is there any possibility that this plugin could use the command line svn binary just like the git jenkins plugin does? Yes, I know that is slightly more work for users who then need to ensure it is installed and the path correct, but vastly less work for the developers of the plugin to keep up with.
> Key: JENKINS-13835
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13835
> Project: Jenkins
> Issue Type: Bug
> Components: subversion
> Reporter: pancake
> Labels: linux, plugin, subversion, windows
>
johan-kees.vliek@pinkroccade.nl (JIRA)
|
_0.png)
|
|||||||
|
This message is automatically generated by JIRA. |
| If you think it was sent incorrectly, please contact your JIRA administrators. |
kk@kohsuke.org (JIRA)
|
|
|||||||
|
This message is automatically generated by JIRA. |
| If you think it was sent incorrectly, please contact your JIRA administrators. |
kk@kohsuke.org (JIRA)
|
||||||||||||
|
This message is automatically generated by JIRA. |
| If you think it was sent incorrectly, please contact your JIRA administrators. |
scm_issue_link@java.net (JIRA)
|
||||||||
|
This message is automatically generated by JIRA. |
| If you think it was sent incorrectly, please contact your JIRA administrators. |
scm_issue_link@java.net (JIRA)
| ||||
|
||||
|
This message is automatically generated by JIRA. |
| If you think it was sent incorrectly, please contact your JIRA administrators. |
kk@kohsuke.org (JIRA)
|
||||||||
|
This message is automatically generated by JIRA. |
| If you think it was sent incorrectly, please contact your JIRA administrators. |
gentoo.integer@gmail.com (JIRA)
| ||||||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
|
||||
|
This message is automatically generated by JIRA. |
| If you think it was sent incorrectly, please contact your JIRA administrators. |
gentoo.integer@gmail.com (JIRA)
|
|||||
|
This message is automatically generated by JIRA. |
| If you think it was sent incorrectly, please contact your JIRA administrators. |
aristedes@java.net (JIRA)
|
||||||||
|
This message is automatically generated by JIRA. |
| If you think it was sent incorrectly, please contact your JIRA administrators. |
gentoo.integer@gmail.com (JIRA)
|
||||||||
|
This message is automatically generated by JIRA. |
| If you think it was sent incorrectly, please contact your JIRA administrators. |
valerie.wagner@sri.com (JIRA)
|
||||||||
|
This message is automatically generated by JIRA. |
| If you think it was sent incorrectly, please contact your JIRA administrators. |
valerie.wagner@sri.com (JIRA)
|
||||||||||
|
This message is automatically generated by JIRA. |
| If you think it was sent incorrectly, please contact your JIRA administrators. |
valerie.wagner@sri.com (JIRA)
|
||||||||
arvid.arntzen@gmail.com (JIRA)
| ||||||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| This message is automatically generated by JIRA. | ||||
chrisl@med-access.net (JIRA)
|
||||||||
leon.moctezuma@gmail.com (JIRA)
| ||||||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
|
||||
linards.liepins@gmail.com (JIRA)
|
||||||||
kutzi@gmx.de (JIRA)
|
||||||||
g.telkamp@domologic.de (JIRA)
|
||||||||
Allan.Eayrs@harmonicinc.com (JIRA)
|
||||||||
dewayne_lavelle@mentor.com (JIRA)
|
||||||||
pancake@java.net (JIRA)
|
||||||||
ghansen990@gmail.com (JIRA)
| ||||||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
|
||||
ghansen990@gmail.com (JIRA)
|
|||||
ghansen990@gmail.com (JIRA)
|
||||||||
pancake@java.net (JIRA)
|
||||||||
ghansen990@gmail.com (JIRA)
|
||||||||
ghansen990@gmail.com (JIRA)
|
|||||
pancake@java.net (JIRA)
|
||||||||
ghansen990@gmail.com (JIRA)
| ||||||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
|
||||
ghansen990@gmail.com (JIRA)
|
|||||
ghansen990@gmail.com (JIRA)
| ||||||||
| ||||
centic@java.net (JIRA)
|
||||||||