-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
Jenkins version: 2.319.1
Priority Sorter Plugin: 4.1.0
Hi,
I recently tried upgrading the priority sorter plugin from 3.6.0 to 4.1.0. This eventually caused Jenkins to become unresponsive and fail to load after about 4 hours of runtime. The Jenkins process was still running when we investigated, but needed a `systemctl restart` to become responsive again. After the restart, Jenkins again slowed and eventually started throwing 500 errors again after another 4-8 hours. Downgrading the plugin back to version 3.6.0 brought it back to a place of stability.
Sorry that it failed like that. Pull requests that have been merged between 3.6.0 and 4.1.0 include:
JENKINS-64694-fix-plugin (UI form changes)I don't see any of those that seem obviously like they would cause a performance regression or a dramatic change of behavior. Dependencies are updated, UI forms are updated, and there are some changes in https://github.com/jenkinsci/priority-sorter-plugin/pull/51/files that are intended to remain binary compatible.