[Regression] Non-unique IDs

[Basil Crow]

jenkinsci/jenkins#5923 introduced a regression concerning non-unique IDs, and jenkinsci/jenkins#7631 fixed the first regression but introduced a second regression, breaking compatibility with multiple critical plugins in violation of the Compatibility matters section of the Project Governance Document. This has caused disruption for end users, who are no longer able to upgrade past 2.390 to the latest weekly release.

This new regression has not yet reached the stable (LTS) line, currently scheduled to ship in May. To ensure that the next LTS release ships without this new regression, options include:

• Rolling forward by adapting the known broken plugins to the change in behavior and releasing new versions, as well as doing a systematic search to verify no other plugins are affected
• Rolling backward to the status quo as of 2.390 by reverting https://github.com/jenkinsci/jenkins/pull/7631
• Rolling backward to the status quo as of 2.334 by reverting both https://github.com/jenkinsci/jenkins/pull/7631 and https://github.com/jenkinsci/jenkins/pull/5923

[Jesse Glick]

https://github.com/jenkinsci/jenkins/pull/7823 is a straightforward fix addressing at least one reported case of regression, with no need to revert anything or modify plugins. There could of course be unrelated issues.

[Mark Waite]

On Friday, April 7, 2023 at 8:59:46 PM UTC-6 Jesse Glick wrote:

https://github.com/jenkinsci/jenkins/pull/7823 is a straightforward fix addressing at least one reported case of regression, with no need to revert anything or modify plugins. There could of course be unrelated issues.

I've confirmed the fix works for the credentials binding plugin and the text file operations plugin.  I was unable to duplicate the issue with the gradle plugin, so cannot answer if the fix resolves that issue.

Mark Waite