[JENKINS-25934] Add ability to set a comment with any installed plugin or "lock" a plugin

[timja]

Been bit several times recently by accidentially upgrading Mercurial plugin, which triggers JENKINS-25523 error. This has also hurt me in past with some other plugins.

It would be really nice to be able to do one of the following:

1. Set a comment/NOTE that would be displayed next to any installed plugin so that I could put a warning to myself "DO NOT UPGRADE - breaks compatability with X" next to a plugin that I know cannot be upgraded, or other comments about the plugin such as if I'm trying to make notes about where certain plugins are used.

or

2. Allow "locking" a plugin so that it cannot be upgraded unless I unlock it first.

---

Originally reported by nneul, imported from: Add ability to set a comment with any installed plugin or "lock" a plugin

• status: Open
• priority: Minor
• resolution: Unresolved
• imported: 2022/01/10

[timja]

danielbeck:

Appears to be a use case with very limited appeal to most users. ("Skip this version" may be better anyway.) May be possible to add in a plugin, once plugin manager columns are made extensible, which they are not at the moment.

Possible workarounds:

• If you know how, create a build identical to your version of mercurial plugin but give it a special version number as indicator that it's super special and should not be replaced without thinking.
• Simple Theme plugin may allow you to add that bit of CSS/JS
• If you have Jenkins Enterprise, check out Update Center Plugin to run your own UC with only approved updates provided
• Filter the JSON received from updates.jenkins-ci.org to exclude mercurial in some way, e.g. through a proxy, or by running a Groovy script in Jenkins that discards the mercurial update info from memory.