-
Bug
-
Resolution: Unresolved
-
Major
-
None
Jenkins should refuse to start up when there are plugin files (hpi/jpi) that file names not matching their contents in the plugins/ directory, as that can lead to confusion about what is installed.
Original description
Upgrading Jenkins from 2.85 to 2.97+ (I tried with 2.97 and 2.105) downloads script-security.jpi version 1.18 and loads it even if script-security.latest.hpi (version 1.40) is in the plugins folder. Deleting script-security.jpi fixes the issue.
Jenkins error log is the same as in . Since that issue is fixed, I'm wondering if this is a regression.JENKINS-48604