[JENKINS-18932] Problems updating subversion plugin/starting Jenkins

We are running Jenkins on Windows 7 on WebSphere 7 and have a mutitude of problems with updating plugins because of one thing, as it seems.

In .jenkins\plugins\subversion\WEB-INF\lib there is antlr-runtime-3.4.jar which is locket in some way when Jenkis tries to update subversion. I am not sure if this is a special problem of Windows/WebSphere but because of this, we have also Problems after updating other plugins or restarting Jenkins - the plugins are just not available and if you don't be careful, you lose all your subversion settings and can reconfigure subversion manually again.

It would be very helpful if the update/plugin-start process would be a little bit more fault tolerant, so that not everything else is omittet after a restart especially as it seems that this specific jar is absolutely irrelevant and not changed during the update.

We have also weird results after such an issue that Jenkins is somehow set back to older versions of plugins we already had installed successfully.

---
Originally reported by pueffl, imported from: Problems updating subversion plugin/starting Jenkins

• status: Open
  
• priority: Major
  
• component(s): subversion-plugin
  
• resolution: Unresolved
  
• votes: 0
  
• watchers: 1
  
• imported: 20251212-090250
  

Raw content of original issue

We are running Jenkins on Windows 7 on WebSphere 7 and have a mutitude of problems with updating plugins because of one thing, as it seems.


In .jenkins\plugins\subversion\WEB-INF\lib there is antlr-runtime-3.4.jar which is locket in some way when Jenkis tries to update subversion. I am not sure if this is a special problem of Windows/WebSphere but because of this, we have also Problems after updating other plugins or restarting Jenkins - the plugins are just not available and if you don't be careful, you lose all your subversion settings and can reconfigure subversion manually again. 


It would be very helpful if the update/plugin-start process would be a little bit more fault tolerant, so that not everything else is omittet after a restart especially as it seems that this specific jar is absolutely irrelevant and not changed during the update.


We have also weird results after such an issue that Jenkins is somehow set back to older versions of plugins we already had installed successfully.

• environment: Windows 7 64 bit / WebSphere 7