-
Bug
-
Resolution: Not A Defect
-
Major
The jenkins update center is serving the wrong update-center.json file for pinned versions. As a result automation that depends on this file to determine the latest compatible version of a plugin for a particular jenkins version (such as the plugin manager CLI) may pull in a plugin version that is too high and requires a newer Jenkins core version.
As far as I can tell there is no place to obtain the actual update-center.json file for 2.277.3 once a newer LTS is released.
Expected:
- Hit https://updates.jenkins.io/update-center.json?version=2.277.3
- Get redirected to https://updates.jenkins.io/dynamic-stable-2.277.3/update-center.json
- Json should only contain plugins compatible with 2.277.3 (example: configuration-as-code:1.50)
Actual:
- Hit https://updates.jenkins.io/update-center.json?version=2.277.3
- Get redirected to https://updates.jenkins.io/dynamic-stable-2.277.3/update-center.json
- Json may contain plugins that are not compatible with 2.277.3 (example: configuration-as-code:1.51)
[JENKINS-66223] Jenkins update center version redirect for update-center.json serves wrong version
Description |
Original:
The jenkins update center is serving the wrong update-center.json file for pinned versions. As a result automation that depends on this file to determine the latest compatible version of a plugin for a particular jenkins version may pull in a plugin version that is too high and requires a newer Jenkins core version.
As far as I can tell there is no place to obtain the actual update-center.json file for 2.277.3 once a newer LTS is released. Expected: # Hit https://updates.jenkins.io/update-center.json?version=2.277.3 # Get redirected to https://updates.jenkins.io/dynamic-stable-2.277.3/update-center.json # Observe actual version in json to be 2.277.3 Actual: # Hit https://updates.jenkins.io/update-center.json?version=2.277.3 # Get redirected to https://updates.jenkins.io/dynamic-stable-2.277.3/update-center.json # Observe actual version in json to be different (at time of writing 2.289.2) |
New:
The jenkins update center is serving the wrong update-center.json file for pinned versions. As a result automation that depends on this file to determine the latest compatible version of a plugin for a particular jenkins version (such as the plugin manager CLI) may pull in a plugin version that is too high and requires a newer Jenkins core version.
As far as I can tell there is no place to obtain the actual update-center.json file for 2.277.3 once a newer LTS is released. Expected: # Hit https://updates.jenkins.io/update-center.json?version=2.277.3 # Get redirected to https://updates.jenkins.io/dynamic-stable-2.277.3/update-center.json # Observe actual version in json to be 2.277.3 Actual: # Hit https://updates.jenkins.io/update-center.json?version=2.277.3 # Get redirected to https://updates.jenkins.io/dynamic-stable-2.277.3/update-center.json # Observe actual version in json to be different (at time of writing 2.289.2) |
Summary | Original: Jenkins update center version redirect for udate-center.json serves wrong version | New: Jenkins update center version redirect for update-center.json serves wrong version |
Description |
Original:
The jenkins update center is serving the wrong update-center.json file for pinned versions. As a result automation that depends on this file to determine the latest compatible version of a plugin for a particular jenkins version (such as the plugin manager CLI) may pull in a plugin version that is too high and requires a newer Jenkins core version.
As far as I can tell there is no place to obtain the actual update-center.json file for 2.277.3 once a newer LTS is released. Expected: # Hit https://updates.jenkins.io/update-center.json?version=2.277.3 # Get redirected to https://updates.jenkins.io/dynamic-stable-2.277.3/update-center.json # Observe actual version in json to be 2.277.3 Actual: # Hit https://updates.jenkins.io/update-center.json?version=2.277.3 # Get redirected to https://updates.jenkins.io/dynamic-stable-2.277.3/update-center.json # Observe actual version in json to be different (at time of writing 2.289.2) |
New:
The jenkins update center is serving the wrong update-center.json file for pinned versions. As a result automation that depends on this file to determine the latest compatible version of a plugin for a particular jenkins version (such as the plugin manager CLI) may pull in a plugin version that is too high and requires a newer Jenkins core version.
As far as I can tell there is no place to obtain the actual update-center.json file for 2.277.3 once a newer LTS is released. Expected: # Hit https://updates.jenkins.io/update-center.json?version=2.277.3 # Get redirected to https://updates.jenkins.io/dynamic-stable-2.277.3/update-center.json # Observe actual version in json to be 2.277.3. Json should only contain plugins compatible with 2.277.3 Actual: # Hit https://updates.jenkins.io/update-center.json?version=2.277.3 # Get redirected to https://updates.jenkins.io/dynamic-stable-2.277.3/update-center.json # Observe actual version in json to be different (at time of writing 2.289.2). Json may contain plugins that are not compatible with 2.277.3 |
Description |
Original:
The jenkins update center is serving the wrong update-center.json file for pinned versions. As a result automation that depends on this file to determine the latest compatible version of a plugin for a particular jenkins version (such as the plugin manager CLI) may pull in a plugin version that is too high and requires a newer Jenkins core version.
As far as I can tell there is no place to obtain the actual update-center.json file for 2.277.3 once a newer LTS is released. Expected: # Hit https://updates.jenkins.io/update-center.json?version=2.277.3 # Get redirected to https://updates.jenkins.io/dynamic-stable-2.277.3/update-center.json # Observe actual version in json to be 2.277.3. Json should only contain plugins compatible with 2.277.3 Actual: # Hit https://updates.jenkins.io/update-center.json?version=2.277.3 # Get redirected to https://updates.jenkins.io/dynamic-stable-2.277.3/update-center.json # Observe actual version in json to be different (at time of writing 2.289.2). Json may contain plugins that are not compatible with 2.277.3 |
New:
The jenkins update center is serving the wrong update-center.json file for pinned versions. As a result automation that depends on this file to determine the latest compatible version of a plugin for a particular jenkins version (such as the plugin manager CLI) may pull in a plugin version that is too high and requires a newer Jenkins core version.
As far as I can tell there is no place to obtain the actual update-center.json file for 2.277.3 once a newer LTS is released. Expected: # Hit https://updates.jenkins.io/update-center.json?version=2.277.3 # Get redirected to https://updates.jenkins.io/dynamic-stable-2.277.3/update-center.json # Json should only contain plugins compatible with 2.277.3 Actual: # Hit https://updates.jenkins.io/update-center.json?version=2.277.3 # Get redirected to https://updates.jenkins.io/dynamic-stable-2.277.3/update-center.json # Json may contain plugins that are not compatible with 2.277.3 |
Description |
Original:
The jenkins update center is serving the wrong update-center.json file for pinned versions. As a result automation that depends on this file to determine the latest compatible version of a plugin for a particular jenkins version (such as the plugin manager CLI) may pull in a plugin version that is too high and requires a newer Jenkins core version.
As far as I can tell there is no place to obtain the actual update-center.json file for 2.277.3 once a newer LTS is released. Expected: # Hit https://updates.jenkins.io/update-center.json?version=2.277.3 # Get redirected to https://updates.jenkins.io/dynamic-stable-2.277.3/update-center.json # Json should only contain plugins compatible with 2.277.3 Actual: # Hit https://updates.jenkins.io/update-center.json?version=2.277.3 # Get redirected to https://updates.jenkins.io/dynamic-stable-2.277.3/update-center.json # Json may contain plugins that are not compatible with 2.277.3 |
New:
The jenkins update center is serving the wrong update-center.json file for pinned versions. As a result automation that depends on this file to determine the latest compatible version of a plugin for a particular jenkins version (such as the plugin manager CLI) may pull in a plugin version that is too high and requires a newer Jenkins core version.
As far as I can tell there is no place to obtain the actual update-center.json file for 2.277.3 once a newer LTS is released. Expected: # Hit https://updates.jenkins.io/update-center.json?version=2.277.3 # Get redirected to https://updates.jenkins.io/dynamic-stable-2.277.3/update-center.json # Json should only contain plugins compatible with 2.277.3 (example: configuration-as-code:1.50) Actual: # Hit https://updates.jenkins.io/update-center.json?version=2.277.3 # Get redirected to https://updates.jenkins.io/dynamic-stable-2.277.3/update-center.json # Json may contain plugins that are not compatible with 2.277.3 (example: configuration-as-code:1.51) |
Resolution | New: Not A Defect [ 7 ] | |
Status | Original: Open [ 1 ] | New: Closed [ 6 ] |
Closed due to user confusion. The core version reported in the json is the version of the latest core - not the version that this json represents.