-
Bug
-
Resolution: Fixed
-
Blocker
-
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.
Ruthann Dolinka
created issue -
Ruthann Dolinka
made changes -
| Summary | Original: The Subversion plugin has stopped working, no option to select subversion in the Source Code Management or Configure System. | New: The Subversion plugin has stopped working, no option in Source Code Management or Configure System. |
| Priority | Original: Major [ 3 ] | New: Blocker [ 1 ] |
Ruthann Dolinka
made changes -
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: Open [ 1 ] | New: Fixed but Unreleased [ 10203 ] |
Ruthann Dolinka
made changes -
| 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. ] |