Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[JENKINS-66938] Allow 2 or more priority definitions to be saved #88

Merged
merged 4 commits into from
Nov 27, 2021

Conversation

MarkEWaite
Copy link
Contributor

@MarkEWaite MarkEWaite commented Nov 26, 2021

JENKINS-66938 Save non-trivial priority definitions

  • Fix for view based priority sorting jelly
  • [JENKINS-66938] Allow save of 2+ priority definitions

Special thanks to @monluk for the April 2021 fix to one of the issues discovered here.

See also:

  • JENKINS-67218 - Unable to store priority sorter configuration
  • JENKINS-65859 - "Priority Sorter Plugin" broken in 2.277.4 (though this fix does not resolve the issue described in that report)

monluk and others added 4 commits April 19, 2021 22:30
The tables to divs fixes in release 4.0.0 of the plugin had the side
effect of preventing the second or later save of priority definitions
that contained more than one priority.

In my example, I defined a "High" priority, a "Low" priority, and a
"Default" priority.  When trying to save that definition, it initially
succeeds, then fails later attempts to save it.

It is unclear why the assignment of a class to the HTML select element
would cause the Stapler response to include unexpected data.
@MarkEWaite
Copy link
Contributor Author

MarkEWaite commented Nov 26, 2021

@timja I don't understand why these changes resolve the issue (especially the removal of the class on the HTML select element), but after many different tests, it seems to be that this set of changes resolves https://issues.jenkins.io/browse/JENKINS-66938 and https://issues.jenkins.io/browse/JENKINS-67218 .

@timja
Copy link
Member

timja commented Nov 27, 2021

I can have a look next week, removing the class is weird

@MarkEWaite
Copy link
Contributor Author

Thanks @timja . I'm going to release a new version of the plugin with this change so that users are unblocked. When we understand the root cause of the issue, we can restore the class and release it.

@MarkEWaite MarkEWaite merged commit 76bd185 into jenkinsci:master Nov 27, 2021
@MarkEWaite MarkEWaite deleted the fix-form-save branch November 27, 2021 14:52
@MarkEWaite MarkEWaite added bug Incorrect or flawed behavior and removed bugfix labels Nov 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Incorrect or flawed behavior
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants