Code changed in jenkins
User: Jesse Glick
Path:
test/src/test/java/hudson/model/ApiTest.java
http://jenkins-ci.org/commit/jenkins/ac80ef27ddd8307d3f57d1185868ac8d92df88a1
Log:
JENKINS-27607 Reproduced in test.

Code changed in jenkins
User: Jesse Glick
Path:
changelog.html
core/src/main/java/hudson/model/Api.java
test/src/test/java/hudson/model/ApiTest.java
http://jenkins-ci.org/commit/jenkins/bd4d15785f06e58db5e5a72a091c78411e734dfa
Log:
JENKINS-27607 Noting merge of #1623.

Compare: https://github.com/jenkinsci/jenkins/compare/e54b19d87231...bd4d15785f06

If backporting, beware that the trunk diff does not show the bump of Stapler to 1.236 as here and here, which would be needed for older versions.

Integrated in jenkins_main_trunk #4031
JENKINS-27607 Reproduced in test. (Revision ac80ef27ddd8307d3f57d1185868ac8d92df88a1)

Result = SUCCESS
jesse glick : ac80ef27ddd8307d3f57d1185868ac8d92df88a1
Files :

• test/src/test/java/hudson/model/ApiTest.java

Any ETA on when this will make its way into a new LTS point build? Kind of less than ideal that the fix for several critical security vulnerabilities breaks a rather substantial piece of functionality.

olivergondza just rejected it a few days ago for 1.596.3, I am guessing because it is too new and did not have the requisite two-week soaking period. That would mean it would have to wait till the next line, something like 1.608.1 (TBD). Bring up on jenkinsci-dev if you feel this needs to be in 1.596.3.

(Do you say that this was a regression from an earlier Jenkins release? My impression was that it was always this way, and Chrome just recently started enforcing the content type. Issues with the regression label deserve special consideration.)

FYI, *.ci.cloudbees.com are already running this patch.

This is part of 1.609, next LTS baseline.