The latest update of the Subversion plugin causes a class cast exception in the Multiple SCM plugin. If subversion is selected as one of the SCM sources in the multiple scm plugin a class cast exception generates the attached logs when updating or checking out new code.

      For the moment we have rolled back our Subversion plugin to 2.4.5 to work around this issue.

          [JENKINS-26303] Not compatible with Subversion plugin 2.5

          Dave Taddei created issue -
          Per Arnold Blaasmo made changes -
          Priority Original: Major [ 3 ] New: Critical [ 2 ]

          I consider this to be a critical bug since it make the plugin not work.

          Per Arnold Blaasmo added a comment - I consider this to be a critical bug since it make the plugin not work.

          Issue confirmed. Plugin not working ATM.

          Alexander Ziller added a comment - Issue confirmed. Plugin not working ATM.
          Per Arnold Blaasmo made changes -
          Labels Original: exception plugin New: exception multiple-scms plugin subversion

          I see that there is this pull request against MultiSCM which might fix
          the problem:

          https://github.com/jenkinsci/multiple-scms-plugin/pull/6

          I'm not sure though if the Subversion 2.5 plugin has introduced new bugs
          which caused this breakage.

          Craig Rodrigues added a comment - I see that there is this pull request against MultiSCM which might fix the problem: https://github.com/jenkinsci/multiple-scms-plugin/pull/6 I'm not sure though if the Subversion 2.5 plugin has introduced new bugs which caused this breakage.

          I submitted this fix to the MultiSCM plugin:

          https://github.com/jenkinsci/multiple-scms-plugin/pull/7

          I have a build of the plugin with my fix here:
          https://people.freebsd.org/~rodrigc/JENKINS-26303/

          Can you try it and provide feedbacK?

          Craig Rodrigues added a comment - I submitted this fix to the MultiSCM plugin: https://github.com/jenkinsci/multiple-scms-plugin/pull/7 I have a build of the plugin with my fix here: https://people.freebsd.org/~rodrigc/JENKINS-26303/ Can you try it and provide feedbacK?

          Per Arnold Blaasmo added a comment - - edited

          I have tested your plugin fix, and it works now.

          Per Arnold Blaasmo added a comment - - edited I have tested your plugin fix, and it works now.

          Chris Tea added a comment -

          I tried this fix, it did fix the exception, but somehow I found the changelog was missing for multi-scm build.

          In the xml of one multi-scm build, there were no items for changeSet.
          <changeSet>
          <kind>Multi[git, svn]</kind>
          </changeSet>

          Any idea?

          Chris Tea added a comment - I tried this fix, it did fix the exception, but somehow I found the changelog was missing for multi-scm build. In the xml of one multi-scm build, there were no items for changeSet. <changeSet> <kind>Multi [git, svn] </kind> </changeSet> Any idea?

          Can you provide a sample job with multiple SCM's configured which shows the problem?

          Does your problem sound similar to what this pull request is trying to fix:

          https://github.com/jenkinsci/multiple-scms-plugin/pull/8

          Craig Rodrigues added a comment - Can you provide a sample job with multiple SCM's configured which shows the problem? Does your problem sound similar to what this pull request is trying to fix: https://github.com/jenkinsci/multiple-scms-plugin/pull/8

            Unassigned Unassigned
            drtaddei Dave Taddei
            Votes:
            9 Vote for this issue
            Watchers:
            15 Start watching this issue

              Created:
              Updated:
              Resolved: