• Type: Bug
• Resolution: Fixed
• Priority: Critical
• Component/s: implied-labels-plugin
• Labels:

  None
• Environment:

  Jenkins 2.387.3 or newer with implied labels 278.v7fc7ed998039 and 280.ve218c64f476a_

[JENKINS-72313] Implied label definitions are erased when system configuration is saved

Mark Waite created issue - 2023-11-11 15:49

Collapse comment: Mark Waite added a comment - 2023-11-11 15:51

Mark Waite added a comment - 2023-11-11 15:51

https://github.com/jenkinsci/implied-labels-plugin/pull/165 is the pull request that resolves the issue.

Expand comment: Mark Waite added a comment - 2023-11-11 15:51

Mark Waite added a comment - 2023-11-11 15:51 https://github.com/jenkinsci/implied-labels-plugin/pull/165 is the pull request that resolves the issue.

Mark Waite made changes - 2023-11-11 15:51

Resolution		New: Fixed [ 1 ]
Status	Original: Open [ 1 ]	New: Fixed but Unreleased [ 10203 ]

Mark Waite made changes - 2023-11-11 15:51

Remote Link

New: This issue links to "PR-165 with the fix to not erase implications when system configuration is saved (Web Link)" [ 29021 ]

Mark Waite made changes - 2023-11-11 16:00

Released As		New: https://github.com/jenkinsci/implied-labels-plugin/releases/tag/281.v1322d123c2b_4
Status	Original: Fixed but Unreleased [ 10203 ]	New: Closed [ 6 ]

Mark Waite made changes - 2023-11-11 16:02

Description

Original: When configuration as code support was added, a bug was introduced that erases the label implications when the system configuration page is saved. The bug exists in implied label plugins * https://plugins.jenkins.io/implied-labels/releases/#version_280.ve218c64f476a_ * https://plugins.jenkins.io/implied-labels/releases/#version_278.v7fc7ed998039

New: When configuration as code support was added, a bug was introduced that erases the label implications when the system configuration page is saved. The bug exists in implied label plugins * https://plugins.jenkins.io/implied-labels/releases/#version_280.ve218c64f476a_ * https://plugins.jenkins.io/implied-labels/releases/#version_278.v7fc7ed998039 Users of Jenkins 2.387.3 will either need to downgrade the implied labels plugin to [228.v63b_3f8443d4e|https://github.com/jenkinsci/implied-labels-plugin/releases/tag/228.v63b_3f8443d4e] or upgrade their Jenkins controller to 2.401.3 or newer. The fixed version of implied labels plugin requires Jenkins 2.401.3 or newer

Mark Waite made changes - 2023-11-11 16:02

Description

Original: When configuration as code support was added, a bug was introduced that erases the label implications when the system configuration page is saved. The bug exists in implied label plugins * https://plugins.jenkins.io/implied-labels/releases/#version_280.ve218c64f476a_ * https://plugins.jenkins.io/implied-labels/releases/#version_278.v7fc7ed998039 Users of Jenkins 2.387.3 will either need to downgrade the implied labels plugin to [228.v63b_3f8443d4e|https://github.com/jenkinsci/implied-labels-plugin/releases/tag/228.v63b_3f8443d4e] or upgrade their Jenkins controller to 2.401.3 or newer. The fixed version of implied labels plugin requires Jenkins 2.401.3 or newer

New: When configuration as code support was added, a bug was introduced that erases the label implications when the system configuration page is saved. The bug exists in implied label plugins * [280.ve218c64f476a_|https://plugins.jenkins.io/implied-labels/releases/#version_280.ve218c64f476a_] * [278.v7fc7ed998039|https://plugins.jenkins.io/implied-labels/releases/#version_278.v7fc7ed998039] Users of Jenkins 2.387.3 will either need to downgrade the implied labels plugin to [228.v63b_3f8443d4e|https://github.com/jenkinsci/implied-labels-plugin/releases/tag/228.v63b_3f8443d4e] or upgrade their Jenkins controller to 2.401.3 or newer. The fixed version of implied labels plugin requires Jenkins 2.401.3 or newer

Collapse comment: Valentin Delaye added a comment - 2023-11-11 17:58

Valentin Delaye added a comment - 2023-11-11 17:58

Thanks for creating bug and release

I realized that my Jenkins instance was broken after saving some config by hand which normally I only manage by JCasC

At the same time I also found similar issue on the Kubernetes plugin here : https://issues.jenkins.io/browse/JENKINS-72314 but is related to Cloud configuration page which erase pod template. Probably similar issue that an empty list of pod template is submitted by the form when configuration is saved

Expand comment: Valentin Delaye added a comment - 2023-11-11 17:58

Valentin Delaye added a comment - 2023-11-11 17:58 Thanks for creating bug and release I realized that my Jenkins instance was broken after saving some config by hand which normally I only manage by JCasC At the same time I also found similar issue on the Kubernetes plugin here : https://issues.jenkins.io/browse/JENKINS-72314 but is related to Cloud configuration page which erase pod template. Probably similar issue that an empty list of pod template is submitted by the form when configuration is saved

Collapse comment: Mark Waite added a comment - 2023-11-11 19:41

Mark Waite added a comment - 2023-11-11 19:41

jonesbusy thanks especially to you for finding the root cause of the issue. I would never deduced a connection between saving system configuration and erasing implied labels definition.

Expand comment: Mark Waite added a comment - 2023-11-11 19:41

Mark Waite added a comment - 2023-11-11 19:41 jonesbusy thanks especially to you for finding the root cause of the issue. I would never deduced a connection between saving system configuration and erasing implied labels definition.