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

The Subversion plugin has stopped working, no option in Source Code Management or Configure System.

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Blocker Blocker
    • subversion-plugin
    • None
    • Jenkins 2.346.2 Subversion 2.16.0

      The Subversion plugin has stopped working. I do not get the option to select subversion in the Source Code Management section anymore, and there is no subversion section in Configure System. I have tried uninstalling and reinstalling the subversion plugin, both through the UI and manually through the plugin folder. I have also tried downgrading both the plugin and Jenkins. None of these things have worked.

          [JENKINS-69244] The Subversion plugin has stopped working, no option in Source Code Management or Configure System.

          James Rivord added a comment - - edited

          I would like to second this. I installed 2.16.0 and everything stopped. I have also tried everything I can think of and it is broken.

          James Rivord added a comment - - edited I would like to second this. I installed 2.16.0 and everything stopped. I have also tried everything I can think of and it is broken.

          I was just able to figure out a solution out for this. It seems that you now have to be running Java 11 for the Subversion plugin to work, though the base Jenkins installation still supports Java 8. I was running Java 1.8 and updated to using Amazon Correto Java 11. I noticed this when looking at the system log in Manage Jenkins > System log and saw that the subversion plugin was getting java version errors.

           

          You will have to go in to Jenkins and edit the Java_home directory path to point to the location of your Java 11 home directory. I did this by going into the jenkins.xml located in the user.dir, which for me was located in C:\Program Files\Jenkins, and editing the java.exe path in the file to point to the Java 11 location. You can find the user.dir by going to Manage Jenkins > System Information and searching for user.dir. I also edited the windows environmental variables to include the Java 11 path, though I am not sure if that is necessary for Jenkins to find the path as that alone did not allow Jenkins to find the path.

           

          After doing this, the java.home variable in Manage Jenkins > System Information now pointed to the Java 11 path and the subversion plugin was working correctly.

          Ruthann Dolinka added a comment - I was just able to figure out a solution out for this. It seems that you now have to be running Java 11 for the Subversion plugin to work, though the base Jenkins installation still supports Java 8. I was running Java 1.8 and updated to using Amazon Correto Java 11. I noticed this when looking at the system log in Manage Jenkins > System log and saw that the subversion plugin was getting java version errors.   You will have to go in to Jenkins and edit the Java_home directory path to point to the location of your Java 11 home directory. I did this by going into the jenkins.xml located in the user.dir, which for me was located in C:\Program Files\Jenkins, and editing the java.exe path in the file to point to the Java 11 location. You can find the user.dir by going to Manage Jenkins > System Information and searching for user.dir. I also edited the windows environmental variables to include the Java 11 path, though I am not sure if that is necessary for Jenkins to find the path as that alone did not allow Jenkins to find the path.   After doing this, the java.home variable in Manage Jenkins > System Information now pointed to the Java 11 path and the subversion plugin was working correctly.

          James Rivord added a comment -

          Thank you for this tip. I had updated the jenkins.config to point to the JDK 11. But then when I looked in the System Information it was not using that. I ended up copying the JDK 11 into the jre folder in the jenkins install. Then it started working. Why is there a setting to point to the JRE if it does not use it. Oh well, thank you so much for your help. I am back working again.

          James Rivord added a comment - Thank you for this tip. I had updated the jenkins.config to point to the JDK 11. But then when I looked in the System Information it was not using that. I ended up copying the JDK 11 into the jre folder in the jenkins install. Then it started working. Why is there a setting to point to the JRE if it does not use it. Oh well, thank you so much for your help. I am back working again.

          I also tried adding the JDK in the Manage Jenkins > Global Tool Configuration > JDK, but Jenkins still kept using the path to Java 1.8. It wasn't until I edited the Jenkins.xml file that it started using the JDK 11 path and the JAVA_HOME  variable in System Information changed to point to the JDK 11 path.

          Ruthann Dolinka added a comment - I also tried adding the JDK in the Manage Jenkins > Global Tool Configuration > JDK, but Jenkins still kept using the path to Java 1.8. It wasn't until I edited the Jenkins.xml file that it started using the JDK 11 path and the JAVA_HOME  variable in System Information changed to point to the JDK 11 path.

          Basil Crow added a comment -

          I noticed this when looking at the system log in Manage Jenkins > System log and saw that the subversion plugin was getting java version errors.

          What errors?

          Basil Crow added a comment - I noticed this when looking at the system log in Manage Jenkins > System log and saw that the subversion plugin was getting java version errors. What errors?

          I don't remember what the specific errors were.

          Ruthann Dolinka added a comment - I don't remember what the specific errors were.

          Basil Crow added a comment -

          Does anyone know how to reproduce the problem from scratch on a clean Jenkins installation?

          Basil Crow added a comment - Does anyone know how to reproduce the problem from scratch on a clean Jenkins installation?

          I would think the problem could be reproduced on a Jenkins installation running JDK 8 with the subversion plugin installed. I have not tested this however.

          Ruthann Dolinka added a comment - I would think the problem could be reproduced on a Jenkins installation running JDK 8 with the subversion plugin installed. I have not tested this however.

          Basil Crow added a comment -

          I would think the problem could be reproduced on a Jenkins installation running JDK 8 with the subversion plugin installed.

          But how?

          I have not tested this however.

          Why not? Do you expect others to help you when you have not provided steps to reproduce the problem?

          Basil Crow added a comment - I would think the problem could be reproduced on a Jenkins installation running JDK 8 with the subversion plugin installed. But how? I have not tested this however. Why not? Do you expect others to help you when you have not provided steps to reproduce the problem?

            Unassigned Unassigned
            ruthd Ruthann Dolinka
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: