Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-16750

Job console output does not refresh when job is done

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved (View Workflow)
    • Minor
    • Resolution: Fixed
    • core
    • None
    • Jenkins 1.500 / Tomcat 6 / JDK 1.6.0_18 / Debian 6 / x86
      IE 9
    • Jenkins 2.175

    Description

      While the job is running, the job console stays updated always.
      But when the job is done, the console does not update anymore.
      This means, the console says "Finished: SUCCESS", the blue ball still is flashing and the progress bar is standing in the middle (not at the end).

      This is rather nasty as one thinks "it is not done, as it is still flashing".

      Attachments

        Issue Links

          Activity

            danielbeck I started playing with AJAX reloading of the build header:
            https://github.com/zbynek/jenkins/commit/271574c97b4e1256cd6056a59ff4102d04a911ce
            does the job for the icon and the progress bar, but it would be nice to update more parts of the page in the future. I was thinking some kind of client side (JS) event queue where every component could send events a listen to them would make this extensible, in this particular commit it would allow me to kill the global updateBuildCaptionIcon JS variable that's referenced from different Jelly files. Is there a mechanism to do that already?

            zbynek Zbynek Konecny added a comment - danielbeck I started playing with AJAX reloading of the build header: https://github.com/zbynek/jenkins/commit/271574c97b4e1256cd6056a59ff4102d04a911ce does the job for the icon and the progress bar, but it would be nice to update more parts of the page in the future. I was thinking some kind of client side (JS) event queue where every component could send events a listen to them would make this extensible, in this particular commit it would allow me to kill the global updateBuildCaptionIcon JS variable that's referenced from different Jelly files. Is there a mechanism to do that already?
            danielbeck Daniel Beck added a comment -

            zbynek I encourage you to submit this as a pull request and let it be reviewed by people who understand JS (not me ).

            danielbeck Daniel Beck added a comment - zbynek I encourage you to submit this as a pull request and let it be reviewed by people who understand JS (not me ).
            zbynek Zbynek Konecny added a comment - danielbeck thanks, I submitted a PR https://github.com/jenkinsci/jenkins/pull/3952 .
            oleg_nenashev Oleg Nenashev added a comment -

            It was fixed in Jenkins 2.175

             

            oleg_nenashev Oleg Nenashev added a comment - It was fixed in Jenkins 2.175  
            oleg_nenashev Oleg Nenashev added a comment -

            Thanks for the fix zbynek!

            oleg_nenashev Oleg Nenashev added a comment - Thanks for the fix zbynek !

            People

              kevinburke Kevin Burke
              mkarg Markus KARG
              Votes:
              5 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: