Closed timja closed 7 years ago
Linking to some examples of this, but from this search you can see there at least a dozen cases.
Code changed in jenkins
User: Jesse Glick
Path:
core/src/main/resources/hudson/model/View/main.groovy
core/src/main/resources/hudson/model/View/main.properties
test/src/test/java/hudson/model/ViewTest.java
http://jenkins-ci.org/commit/jenkins/fcf4ca7697b4a5293c95b221669f202621b178f7
Log:
[FIXED JENKINS-41825] Display an informative message, rather than a Groovy exception, when View.getItems fails.
Code changed in jenkins
User: Jesse Glick
Path:
core/src/main/resources/hudson/model/View/main.groovy
core/src/main/resources/hudson/model/View/main.properties
test/src/test/java/hudson/model/ViewTest.java
http://jenkins-ci.org/commit/jenkins/da2f57c7221742bda5a97bf8c026d6b9dd42fcd5
Log:
[FIXED JENKINS-41825] Display an informative message, rather than a Groovy exception, when View.getItems fails.
(cherry picked from commit fcf4ca7697b4a5293c95b221669f202621b178f7)
It is not uncommon for an error to be thrown from View.getItems. Currently Jenkins behaves poorly in this case: it displays an "oops" page with a cryptic stack trace
that has no relation to the real error.
Originally reported by jglick, imported from: Page loads breaks when View.getItems fails