[
https://issues.jenkins-ci.org/browse/JENKINS-13217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160740#comment-160740
]
SCM/JIRA link daemon commented on JENKINS-13217:
------------------------------------------------
Code changed in jenkins
User: Richard Mortimer
Path:
changelog.html
core/src/main/resources/lib/hudson/buildCaption.jelly
http://jenkins-ci.org/commit/jenkins/eb3e288d6e761109c20cf479c80dfb4c69801dbe
Log:
[FIXED JENKINS-13217] Build Status page continues to show flashing "building"
icons after build completion.
> Build Status page continues to show flashing "building" icons after build
> completion
> ------------------------------------------------------------------------------------
>
> Key: JENKINS-13217
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13217
> Project: Jenkins
> Issue Type: Bug
> Components: core
> Affects Versions: current
> Environment: Jenkins 1.456/ Ubuntu 11.10
> Reporter: Richard Mortimer
> Assignee: Richard Mortimer
> Priority: Minor
>
> The main build status page shows a 48x48 icon representing the build status.
> If you visit the page during the build this shows a flashing "build in
> progress" icon. However when the build stops the "build in progress" icon
> continues to be displayed.
> This is due to browser caching behaviour. For example the recent build at the
> following URL
> http://ci.jenkins-ci.org/job/tools_maven-hpi-plugin-maven-2.x/40/
> During the build the relevant markup was
> {code}
> <img height="48" alt="In progress" width="48" src="buildStatus" tooltip="In
> progress" />
> Build #40
> (23-Mar-2012 01:18:30)
> {code}
> The request for buildStatus returned a HTTP 302 redirect to
> {code}
> Location:http://ci.jenkins-ci.org/images/48x48/blue_anime.gif
> {code}
> The combination of a 302 redirect and caching headers in the gif cause the
> browser to not re-request buildStatus within the same browser session.
> http://ci.jenkins-ci.org/job/tools_maven-hpi-plugin-maven-2.x/40/buildStatus
> Note this is unrelated to the recent changes for caching of images etc. I
> have noticed this in the past but have not had time to investigate before now.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
