Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-17616

Performance issue with Subversion plugin - trigger build on SVN commit takes too long

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • subversion-plugin
    • None
    • Windows, Visual SVN

      After upgrade of Jenkins/Subversion plugin from version 1.447/1.39 to version 1.501/1.45, we have noticed significant delay in triggering builds on commit (around 1 minute). We are using notify CI method in our post-commit hooks.Users who do not have jobs configured in Jenkins are being badly impacted, while post commit hook notifies Jenkins.
      Downgrading Subversion plugin back to 1.39 removes this issue, but we would like to be on a higher version as Subversion 1.7 is supported those versions.

          [JENKINS-17616] Performance issue with Subversion plugin - trigger build on SVN commit takes too long

          Sure, here is all my output
          http://justpaste.it/oibx

          Luis Roberto Perez Rios added a comment - Sure, here is all my output http://justpaste.it/oibx

          danielbeck just to confirm, did you see the output? I mean this http://justpaste.it/oibx, is working?

          Luis Roberto Perez Rios added a comment - danielbeck just to confirm, did you see the output? I mean this http://justpaste.it/oibx , is working?

          roberto87, Could you provide a step by step process to reproduce the problem? I'd like to help here.

          Manuel Recena Soto added a comment - roberto87 , Could you provide a step by step process to reproduce the problem? I'd like to help here.

          roberto87 ping? /cc gcadmin

          Manuel Recena Soto added a comment - roberto87 ping? /cc gcadmin

          Daniel Beck added a comment -

          recena From the stack trace it's many projects with many SCM locations. There should be caching going on that limits the number of necessary connections to determine each SCMLocation's UUID (to determine whether the post-commit notification is relevant), but maybe it's broken again?

          Daniel Beck added a comment - recena From the stack trace it's many projects with many SCM locations. There should be caching going on that limits the number of necessary connections to determine each SCMLocation's UUID (to determine whether the post-commit notification is relevant), but maybe it's broken again?

          recena The request to send a SVN poll event is taking long time, more details in the attached log.

          Luis Roberto Perez Rios added a comment - recena The request to send a SVN poll event is taking long time, more details in the attached log.

          roberto87, this issue is too old. I'd like to confirm what version of Subversion Plugin are you using.

          Manuel Recena Soto added a comment - roberto87 , this issue is too old. I'd like to confirm what version of Subversion Plugin are you using.

          recena The version that I have installed is "Jenkins Subversion Plug-in 2.5.2"

          Thank you in advance

          Luis Roberto Perez Rios added a comment - recena The version that I have installed is "Jenkins Subversion Plug-in 2.5.2" Thank you in advance

          recena The version that I have installed is "Jenkins Subversion Plug-in 2.5.2"

          Thank you in advance

          Luis Roberto Perez Rios added a comment - recena The version that I have installed is "Jenkins Subversion Plug-in 2.5.2" Thank you in advance

          roberto87, I'll try to reproduce the bug using 2.5.5.

          Manuel Recena Soto added a comment - roberto87 , I'll try to reproduce the bug using 2.5.5.

            recena Manuel Recena Soto
            gcadmin Glen Core
            Votes:
            3 Vote for this issue
            Watchers:
            11 Start watching this issue

              Created:
              Updated: