-
Bug
-
Resolution: Fixed
-
Major
-
Jenkins 1.509.4
Jenkins 1.532.1 RC1
Firefox 17.0.10 ESR
The error screens shown for invalid configurations after pressing 'Apply' don't work.
Steps to reproduce:
0. Install Jenkins Enterprise with Cloudbees Template Plugin 4.1
1. Create a job template
3. Clear the 'name' attribute's ID field
4. Press 'Apply'
Expected result: Error message shown
Actual result: Huge, empty dialog with title 'Error' shown (error screen seems to appear, but is immediately removed)
- is related to
-
JENKINS-17401 Renaming a job and clicking 'Apply' shows an empty 'Error' pop-over window
-
- Resolved
-
-
JENKINS-19826 Apply button does not work in IE Compat View
-
- Resolved
-
-
JENKINS-21457 Replace description in error dialog instead of appending
-
- Resolved
-
[JENKINS-20772] 'Apply' error screens don't work
Assignee | New: Steven Christou [ schristou ] |
Description |
Original:
The error screens shown for invalid configurations after pressing 'Apply' don't work. Steps to reproduce: 1. Create a freestyle job with a unique, valid name 3. Clear the name in the config screen 4. Press 'Apply' Expected result: Error message shown Actual result: Huge, empty dialog with title 'Error' shown (error screen seems to appear, but is immediately removed) |
New:
The error screens shown for invalid configurations after pressing 'Apply' don't work. Steps to reproduce: 0. Install Jenkins Enterprise with Cloudbees Template Plugin 4.1 1. Create a job template 3. Clear the 'name' attribute's ID field 4. Press 'Apply' Expected result: Error message shown Actual result: Huge, empty dialog with title 'Error' shown (error screen seems to appear, but is immediately removed) |
Assignee | Original: Steven Christou [ schristou ] | New: Kohsuke Kawaguchi [ kohsuke ] |
Link |
New:
This issue is related to |
There are several issues about the errors that (don't) appear in response to some action (
JENKINS-17401,JENKINS-13287,JENKINS-19037, possibly others) but none seem to cover the problem that the error screen is completely useless because it doesn't show the error (e.g. stacktrace).