-
Bug
-
Resolution: Fixed
-
Major
-
Windows 7; Jenkins 1.617 with Subversion Plug-in 2.5.5
Windows Server 2012 R2; Jenkins 2.19.3 with Subversion plugin 2.7.1
Linux x86_64, Jenkins 2.19.4 with Subversion Plugin 2.7.1
Steps to reproduce the bug:
- Install Jenkins 1.617 with Subversion Plug-in 2.5.5
- Declare externals (external_link) on SVN repo
- Create a job that uses a SVN repo with credentials (username/password)
- Setup credential for this repository
- Execute the job
Stack trace:
hudson.util.IOException2: revision check failed on <external_link>
at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:199)
at hudson.scm.SubversionChangeLogBuilder.run(SubversionChangeLogBuilder.java:137)
at hudson.scm.SubversionSCM.calcChangeLog(SubversionSCM.java:722)
at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:857)
at hudson.scm.SCM.checkout(SCM.java:485)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1282)
at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:610)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:532)
at hudson.model.Run.execute(Run.java:1744)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:98)
at hudson.model.Executor.run(Executor.java:374)
- is duplicated by
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
- is related to
-
-
- Open
-
-
-
- Open
-
-
-
- Closed
-
- relates to
-
-
- Reopened
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
- links to
[JENKINS-32167] ISVNAuthentication provider did not provide credentials
Matt Grochowalski
added a comment - Liyaa submitted a pull request to fix this issue:
https://github.com/jenkinsci/subversion-plugin/pull/212 
Andrew Lucas
added a comment - You closed JENKINS-31455 as a duplicate to this one. If this one ever gets worked, be sure to address that it is seen when using external svn references in a build. The first build fails with the authentication error, then the next completes. The cause of the build is lost to the second build, and two builds have to occur.
31455 had some comments that might be useful to keep track of:
smccants added a comment - 2018-02-13 13:59
dimitkoto, as stated in JENKINS-32167, there is no owner or maintainer of this plugin. There is a workaround provided in comments under JENKINS-32167. jglick provided some better feedback code, but I don't think that has ever shipped. I looked at it and wrote a test case demonstrating the problem, but solving it was too complicated for the time I could devote to it.
I don't think anything has changed since then. Wish someone would step up and fix it for us users, but I'm not expecting it until the SVN plugin is totally busted.
Andrew Lucas
added a comment - You closed JENKINS-31455 as a duplicate to this one. If this one ever gets worked, be sure to address that it is seen when using external svn references in a build. The first build fails with the authentication error, then the next completes. The cause of the build is lost to the second build, and two builds have to occur.
31455 had some comments that might be useful to keep track of:
smccants added a comment - 2018-02-13 13:59
dimitkoto , as stated in JENKINS-32167 , there is no owner or maintainer of this plugin. There is a workaround provided in comments under JENKINS-32167 . jglick provided some better feedback code, but I don't think that has ever shipped. I looked at it and wrote a test case demonstrating the problem, but solving it was too complicated for the time I could devote to it.
I don't think anything has changed since then. Wish someone would step up and fix it for us users, but I'm not expecting it until the SVN plugin is totally busted.
I just wanted to point to https://issues.jenkins-ci.org/browse/JENKINS-45801 There are two simple bash scripts to reproduce the defect (or at least a variant of it).
Please feel free to include theses scripts into your build system to verify the defect or it's fix.
Edgars Batna
added a comment - Installed the plugin yesterday and so far going strong. Thanks for the improvement! All jobs went from typically red to typically green/blue.
Edgars Batna
added a comment - Installed the plugin yesterday and so far going strong. Thanks for the improvement! All jobs went from typically red to typically green/blue. 
I used advorsky73 solution from comment-246389 since January 2016. Didn't update Jenkins (still on 1.x), but 2.5.7 version of SVN plugin with that fix works fine. All features seem to work correctly (checkout works with and without externals, changes show up in the build, passing credentials work). Most of the builds in installation of my current company use SVN. And there are many externals in repos used.
It would seem the workaround is a valid solution (as there has been no other solution present) and the exception is a false negative somehow... Could someone push the solution to the official repo and run some automated tests (if there are any for this one).