Managing Plugins page - File copied to JENKINS_HOME/plugins should be .jpi not .hpi

[KalleOlaviNiemitalo]

Problem with the Managing Plugins page, source file

https://www.jenkins.io/doc/book/managing/plugins/#on-the-controller says:

Copy the downloaded .hpi file into the JENKINS_HOME/plugins directory on the Jenkins controller

However, when the update center places files in that directory, it uses the .jpi extension, not .hpi. So if the Jenkins administrator has installed e.g. the Azure AD plugin via the update center and downgrades it by copying the lower version of azure-ad.hpi to that directory, then the directory will have both azure-ad.hpi (lower version, copied by administrator) and azure-ad.jpi (higher version, installed via update center) in it. Jenkins then unpacks the plugin files from azure-ad.hpi, but the update center reads the version information from azure-ad.jpi and does not realize that the plugin has been downgraded.

Possible Solution

Recommend that the Jenkins administrator renames plugin files to end with .jpi when copying them to JENKINS_HOME/plugins.

[321ravi]

@MarkEWaite what i need to change in this all plugins .hpi to .jpi or i have to explain it