|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Code changed in jenkins
User: Jesse Glick
Path:
changelog.html
core/src/main/java/hudson/model/AbstractItem.java
core/src/main/java/jenkins/model/Jenkins.java
core/src/main/java/jenkins/util/ProgressiveRendering.java
core/src/main/resources/hudson/model/Computer/builds.jelly
core/src/main/resources/hudson/model/User/builds.jelly
core/src/main/resources/hudson/model/View/builds.jelly
core/src/main/resources/lib/hudson/buildListTable.jelly
test/src/test/java/hudson/model/MyViewTest.java
test/src/test/java/jenkins/widgets/BuildListTableTest.java
http://jenkins-ci.org/commit/jenkins/ea95434938b2111d8768528823990a78bdc58d3e
Log:
[FIXED JENKINS-19310] Provide correct links for build history inside a folder.
The basic fix is to use ${rootURL} plus full model object URLs rather than relying on ${jobBaseUrl}.
This is made trickier by the fact that the model object URLs are computed inside ProgressiveRendering.compute,
and therefore will not be correct when nondefault views are in the crumb trail unless the original request information is present.
So modifying ProgressiveRendering to preserve a copy of the original request for use during computation.
(This could probably be used to simplify parts of AsynchPeople as well.)
Also improving AbstractItem.getUrl to properly construct a URL including views even when the current page is not inside the item;
it should suffice for some ancestor of the current item (or a view thereof) to be in the ancestor list of this page.