-
Bug
-
Resolution: Unresolved
-
Minor
-
None
It appears that optional dependencies are never upgraded when loading detached and bundled plugins, even if the installed version is older than a version requested by one of the bundled plugins. Discovered by danielbeck while investigating JENKINS-48604, see https://github.com/jenkinsci/jenkins/pull/3201#discussion_r157554680 for the initial comment, and commit eb77e5f for an untested fix.
I don't have an actual example of this in the wild, but here is the idea of how to reproduce:
- Assume a plugin artifactA with two releases: 1.0 and 2.0
- Assume a plugin artifactB, with a single release 1.0, which has an optional dependency on artifactA:2.0
- Create a fresh Jenkins installation and install a plugin artifactA:1.0.
- Upgrade Jenkins using a jenkins.war which has artifactB:1.0 bundled in /WEB-INF/plugins.
- Expected Result: artifactA should be automatically updated to 2.0.
- Actual Result: artifactA is still 1.0.
- relates to
-
-
- Resolved
-
-
-
- Open
-
- links to
[JENKINS-48614] Optional dependencies of bundled and detached plugins are not upgraded if an outdated version is installed
| Link |
New:
This issue relates to |
| Description |
Original:
Discovered by [~danielbeck] while investigating I don't have an actual example of this in the wild, but here is the idea of how to reproduce: # Assume a plugin {{artifactA}} with two releases: 1.0 and 2.0 # Assume a plugin {{artifactB}}, with a single release 1.0, which has an optional dependency on {{artifactA:2.0}} # Create a fresh Jenkins installation and install a plugin {{artifactA:1.0}}. # Upgrade Jenkins using a {{jenkins.war}} which has {{artifactB:1.0}} bundled in {{/WEB-INF/plugins}}. # Expected Result: {{artifactA}} should be automatically updated to 2.0. # Actual Result: {{artifactA}} is still 1.0. |
New:
Discovered by [~danielbeck] while investigating I don't have an actual example of this in the wild, but here is the idea of how to reproduce: # Assume a plugin {{artifactA}} with two releases: 1.0 and 2.0 # Assume a plugin {{artifactB}}, with a single release 1.0, which has an optional dependency on {{artifactA:2.0}} # Create a fresh Jenkins installation and install a plugin {{artifactA:1.0}}. # Upgrade Jenkins using a {{jenkins.war}} which has {{artifactB:1.0}} bundled in {{/WEB-INF/plugins}}. # Expected Result: {{artifactA}} should be automatically updated to 2.0. # Actual Result: {{artifactA}} is still 1.0. |
| Link | New: This issue relates to JENKINS-48615 [ JENKINS-48615 ] |
| Description |
Original:
Discovered by [~danielbeck] while investigating I don't have an actual example of this in the wild, but here is the idea of how to reproduce: # Assume a plugin {{artifactA}} with two releases: 1.0 and 2.0 # Assume a plugin {{artifactB}}, with a single release 1.0, which has an optional dependency on {{artifactA:2.0}} # Create a fresh Jenkins installation and install a plugin {{artifactA:1.0}}. # Upgrade Jenkins using a {{jenkins.war}} which has {{artifactB:1.0}} bundled in {{/WEB-INF/plugins}}. # Expected Result: {{artifactA}} should be automatically updated to 2.0. # Actual Result: {{artifactA}} is still 1.0. |
New:
It appears that optional dependencies are never upgraded when loading detached and bundled plugins, even if the installed version is older than a version requested by one of the bundled plugins. Discovered by [~danielbeck] while investigating I don't have an actual example of this in the wild, but here is the idea of how to reproduce: # Assume a plugin {{artifactA}} with two releases: 1.0 and 2.0 # Assume a plugin {{artifactB}}, with a single release 1.0, which has an optional dependency on {{artifactA:2.0}} # Create a fresh Jenkins installation and install a plugin {{artifactA:1.0}}. # Upgrade Jenkins using a {{jenkins.war}} which has {{artifactB:1.0}} bundled in {{/WEB-INF/plugins}}. # Expected Result: {{artifactA}} should be automatically updated to 2.0. # Actual Result: {{artifactA}} is still 1.0. |
| Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
| Remote Link | New: This issue links to "PR 3202 (Web Link)" [ 19502 ] |
| Status | Original: In Progress [ 3 ] | New: Open [ 1 ] |