• Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • core
    • None
    • Windows Server 2008 R2 Enterprise

      I am having intermittent issues with Jenkins where the dashboard will indicate that a job has never been run even though it has. The files and folders from the previous build(s) are all in place and if I run the build again, it usually updates the status correctly after the build completes. However, that status may go back to indicating that the job has never been built at a later time. Most of the time it is not the latest job/build which loses its status. The status may switch to the correct data after a different job is built, but not always. I have yet to determine any kind of pattern as to which builds are being ignored, much less why. This was happening regularly with version 1.493 and has now started happening with 1.494.

          [JENKINS-16175] Dashboard not showing job status

          This problem had seemingly gone away after I upgraded to 1.496, but now it's happening with 1.497.

          Richard Merrill added a comment - This problem had seemingly gone away after I upgraded to 1.496, but now it's happening with 1.497.

          ...and again with 1.498 on a different Windows 2008 R2 server.

          Richard Merrill added a comment - ...and again with 1.498 on a different Windows 2008 R2 server.

          This issue duplicates JENKINS-15156 Builds Disappear from Build History after Completion that was created earlier, contains much more data, votes, watches and generally gets much more attention. Please consider instead assigning to initial issue instead of to duplicate.

          Nikolay Martynov added a comment - This issue duplicates JENKINS-15156 Builds Disappear from Build History after Completion that was created earlier, contains much more data, votes, watches and generally gets much more attention. Please consider instead assigning to initial issue instead of to duplicate.

          Sorry, didn't find the initial issue in my search before posting this one. I notice that the other issue (and others which duplicate it) don't indicate any progress on determining exactly what is causing the problem, much less a fix for it. :/

          Richard Merrill added a comment - Sorry, didn't find the initial issue in my search before posting this one. I notice that the other issue (and others which duplicate it) don't indicate any progress on determining exactly what is causing the problem, much less a fix for it. :/

          I haven't seen this bug in several months, so I'm assuming one of the fixes did the trick.

          Richard Merrill added a comment - I haven't seen this bug in several months, so I'm assuming one of the fixes did the trick.

            aeschbacher aeschbacher
            richardm_tx Richard Merrill
            Votes:
            1 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: