-
Bug
-
Resolution: Fixed
-
Major
It appears that Jenkins no longer records when it is upgraded, and every restart of ci.jenkins.io now logs something like
2021-04-09 12:46:46.843+0000 [id=30] INFO hudson.PluginManager#loadDetachedPlugins: Upgrading Jenkins. The last running version was 2.263.4. This Jenkins is version 2.277.2. 2021-04-09 12:46:46.922+0000 [id=30] INFO hudson.PluginManager#loadDetachedPlugins: Upgraded Jenkins from version 2.263.4 to version 2.277.2. Loaded detached plugins (and dependencies): []
Probably the same cause as JENKINS-65149.
This will cause previously uninstalled detached plugins to be installed again (in addition to the confusing log message).
- relates to
-
-
- Open
-
[JENKINS-65329] Jenkins no longer records updates
| Link | New: This issue relates to JENKINS-65149 [ JENKINS-65149 ] |
| Labels | Original: regression | New: lts-candidate regression |
| Priority | Original: Critical [ 2 ] | New: Major [ 3 ] |
However, it will reinstall manually uninstalled detached plugins.
2021-04-09 13:08:40.850+0000 [id=29] INFO hudson.PluginManager#loadDetachedPlugins: Upgrading Jenkins. The last running version was 2.176.4. This Jenkins is version 2.277.2. 2021-04-09 13:08:40.954+0000 [id=29] INFO hudson.PluginManager#loadDetachedPlugins: Upgraded Jenkins from version 2.176.4 to version 2.277.2. Loaded detached plugins (and dependencies): [trilead-api.hpi]
| Description |
Original:
It appears that Jenkins no longer records when it is upgraded, and every restart of ci.jenkins.io now logs something like
{noformat} 2021-04-09 12:46:46.843+0000 [id=30] INFO hudson.PluginManager#loadDetachedPlugins: Upgrading Jenkins. The last running version was 2.263.4. This Jenkins is version 2.277.2. 2021-04-09 12:46:46.922+0000 [id=30] INFO hudson.PluginManager#loadDetachedPlugins: Upgraded Jenkins from version 2.263.4 to version 2.277.2. Loaded detached plugins (and dependencies): [] {noformat} Probably the same cause as JENKINS-65149. This probably breaks detaching plugins: I expect that any plugins detached in the version jump are likely to be detached during every startup, possibly resulting in downgrades. |
New:
It appears that Jenkins no longer records when it is upgraded, and every restart of ci.jenkins.io now logs something like
{noformat} 2021-04-09 12:46:46.843+0000 [id=30] INFO hudson.PluginManager#loadDetachedPlugins: Upgrading Jenkins. The last running version was 2.263.4. This Jenkins is version 2.277.2. 2021-04-09 12:46:46.922+0000 [id=30] INFO hudson.PluginManager#loadDetachedPlugins: Upgraded Jenkins from version 2.263.4 to version 2.277.2. Loaded detached plugins (and dependencies): [] {noformat} Probably the same cause as JENKINS-65149. This will cause previously uninstalled detached plugins to be installed again (in addition to the confusing log message). |
Alan Sparks
added a comment - This issue continues with 2.277.3 LTS update, jenkins.install.InstallUtil.lastExecVersion is not updated.
Alan Sparks
added a comment - This issue continues with 2.277.3 LTS update, jenkins.install.InstallUtil.lastExecVersion is not updated. What I've faced:
- Install 2.277.1
- Stop it
- Start a 2.277.2 using the same Jenkins Home
- Stop it
- Start the 2.277.2 again
- ...
You always see:
INFO hudson.PluginManager#loadDetachedPlugins: Upgrading Jenkins. The last running version was 2.277.1. This Jenkins is version 2.277.2. INFO hudson.PluginManager#loadDetachedPlugins: Upgraded Jenkins from version 2.277.1 to version 2.277.2. Loaded detached plugins (and dependencies): []
The jenkins.install.InstallUtil.lastExecVersion or jenkins.install.UpgradeWizard.state files are never updated. It doesn’t happen with latest versions (2.288 -> 2.289)
It doesn’t happen with latest versions (2.288 -> 2.289)
So I guess we don't need this issue anymore if it's fixed on weeklies, since the 2.277.x line is done?
Impact seems more limited than I expected. First restart:
Second restart:
So at least this doesn't result in plugin downgrades.