Details
-
Bug
-
Status: Closed (View Workflow)
-
Blocker
-
Resolution: Fixed
-
-
1.15
Description
The Notification plugin breaks the UI and prevents configurations from being saved after upgrade to 2.277+
The symptoms are that:
UI does not render correctly and configuration changes are not saved.
This has been tested on:
- notification:1.14 'Jenkins Notification plugin'
- Jenkins 2.277.4
Workaround
- Disabling the plugin fixes the configuration update issue.
Attachments
Issue Links
- is caused by
-
JENKINS-56109 Jenkins Core: Change Jenkins configuration UI from tables to divs
-
- Closed
-
Activity
| Field | Original Value | New Value |
|---|---|---|
| Link |
This issue is caused by |
| Description | The Notification plugin breaks the UI and prevents configurations from being saved after upgrde to 2.277+ | The Notification plugin breaks the UI and prevents configurations from being saved after upgrade to 2.277+ |
| Priority | Major [ 3 ] | Blocker [ 1 ] |
| Description | The Notification plugin breaks the UI and prevents configurations from being saved after upgrade to 2.277+ |
The Notification plugin breaks the UI and prevents configurations from being saved after upgrade to 2.277+
This has been tested on: * notification:1.14 'Jenkins Notification plugin' * Jenkins 2.277.4 *Workaround* * Disabling the plugin fixes the configuration update issue. |
| Description |
The Notification plugin breaks the UI and prevents configurations from being saved after upgrade to 2.277+
This has been tested on: * notification:1.14 'Jenkins Notification plugin' * Jenkins 2.277.4 *Workaround* * Disabling the plugin fixes the configuration update issue. |
The Notification plugin breaks the UI and prevents configurations from being saved after upgrade to 2.277+
The symptoms are that: UI does not render correctly and configuration changes are not saved. This has been tested on: * notification:1.14 'Jenkins Notification plugin' * Jenkins 2.277.4 *Workaround* * Disabling the plugin fixes the configuration update issue. |
Ray Kivisto
made changes -
| Labels | tables-to-divs-regression |
mcardenasblanco when you say "temporarily" do you mean until there is a fix? Do you mean turning it off and then on resolves the issue?
Martin Beller
made changes -
| Assignee | Martin Beller [ mbeller ] |
Martin Beller
made changes -
| Assignee | Martin Beller [ mbeller ] | Manuel Cardenas [ mcardenasblanco ] |
douglasawh the notification plugin must be disabled until a fix is available. If you'd like to submit a fix, instructions are available on jenkins.io. The change needs to be in the config.jelly file. The last release of the plugin was May 2022, so there is some activity on the plugin that might get a proposed fix merged.
Alternatives for the fix include:
- Update the minimum Jenkins version to 2.346.3 and change the <table> tags to <div> tags in the config.jelly file
- Insert conditionals into config.jelly to support older Jenkins versions as described in the tables to divs migration guide
I prefer the first option because it seems simpler and easier to maintain. I don't know what the maintainers of the plugin prefer.
S
added a comment -
I have tested the version 1.15 released on 14 July 2021(a release 1.17 has been released 2 weeks ago) on Jenkins controller 2.346.4.1.
It seems to solve the issue described as the "Save button" is no longer frozen.
S
added a comment -
I have tested the version 1.15 released on 14 July 2021(a release 1.17 has been released 2 weeks ago) on Jenkins controller 2.346.4.1.
It seems to solve the issue described as the "Save button" is no longer frozen.
As far as I can tell from reading the source code, div based form layout conditionals have been added. Thanks!
| Released As | 1.15 | |
| Resolution | Fixed [ 1 ] | |
| Status | Open [ 1 ] | Closed [ 6 ] |
Notification plugin breaks the UI after the fix. The workaround is to disable the plugin temporarily.