I'd like to help triage these as well, the subversion plugin was on my priority list for the Bug Triage Team since it was second only to core in terms of open issues.
Would JavaHL [1] be a solution that could cut down on the amount of parsing that would need to be done by the plugin? It would still require a native subversion (library) to be on the system. 1 - http://subversion.apache.org/docs/javahl/latest/ On Thu, May 25, 2017 at 6:01 AM Jesse Glick <jgl...@cloudbees.com> wrote: > On Wed, May 24, 2017 at 8:02 PM, James Dumay <jdu...@cloudbees.com> wrote: > > are there any active maintainers for this plugin > > Not that I am aware of. > > > OK if I triaged the outstanding tickets? > > I cannot imagine anyone objecting to your volunteering such work. > > The broader issue I see is JENKINS-28251: the SVNKit-based > implementation is the source of countless problems, and given limited > development resources there is no way they will all get fixed. IMO the > only sustainable path for this plugin would be to deprecate that mode > and switch by default to a command-line implementation, as the Git > plugin does. This would involve a block of significant effort, but > after that further problems in the execution of SCM operations (the > main source of complaints for the plugin) would reduce to checking > whether the plugin is running the right command or not, a much more > approachable question for casual contributors. (The situation is > trickier for multibranch operations in `SubversionSCMSource`: we would > need to decide whether indexing operations should remain on SVNKit, or > whether the master would be required to have `svn` installed. The Git > plugin takes the former approach, the Mercurial plugin the latter.) > > By the way in your message I think you were attempting to post a > search link, but it did not come out that way. > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-dev+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr0MxXEzjHsLGHWBHpQQEhC6AKVLwgzW-X4cwg6GD5rDUw%40mail.gmail.com > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPiUgVdgncmBgX6CXJ6tVcp5%3Di8r1P5t-aONKqQxY%3DSv4FeK6w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
