• Icon: Bug Bug
    • Resolution: Incomplete
    • Icon: Critical Critical
    • core
    • Jenkins 1.506

      Revisiting https://issues.jenkins-ci.org/browse/JENKINS-15156 once again.

      The issue still persists. Builds are disappearing from history, even though they are present on the disk. They reappear after Jenkins restart.

        1. check_invalid_builds.sh
          3 kB
        2. check_missing_builds.sh
          1 kB
        3. check_invalid_builds.sh
          3 kB
        4. check_missing_builds.sh
          1 kB
        5. plugin1.bmp
          plugin1.bmp
          3.65 MB
        6. plugin2.bmp
          plugin2.bmp
          1.92 MB
        7. plugin3.bmp
          plugin3.bmp
          3.65 MB

          [JENKINS-17265] Builds disappearing from history

          Alex Vesely created issue -
          Nikolay Martynov made changes -
          Link New: This issue is related to JENKINS-15156 [ JENKINS-15156 ]
          Jesse Glick made changes -
          Link New: This issue is related to JENKINS-8754 [ JENKINS-8754 ]

          Harpreet Nain added a comment -

          We have the same issue on version 1.494, 1.499 and 1.502. We dont have any master/slave configuration in place. The job history seems to come back after we do a "Reload Configuration from Disk"

          Harpreet Nain added a comment - We have the same issue on version 1.494, 1.499 and 1.502. We dont have any master/slave configuration in place. The job history seems to come back after we do a "Reload Configuration from Disk"

          Same issue on 1.506, job history for some jobs disappears. Selecting "Reload Configuration from Disk" brings the history back.

          Matt Williamson added a comment - Same issue on 1.506, job history for some jobs disappears. Selecting "Reload Configuration from Disk" brings the history back.

          kflorian added a comment -

          Confirming this on Jenkins 1.505, running on Linux with Linux slaves.
          Build results seem to disappear from some jobs, while they show up as usual on others.
          Seems to happen even more frequently in 1.505 than in the version(s) before!
          Also confirming that "Reload Configuration from Disk" brings back the history.

          kflorian added a comment - Confirming this on Jenkins 1.505, running on Linux with Linux slaves. Build results seem to disappear from some jobs, while they show up as usual on others. Seems to happen even more frequently in 1.505 than in the version(s) before! Also confirming that "Reload Configuration from Disk" brings back the history.

          Jose Sa added a comment -

          Please notice that "Reload from disk" may be unsafe if you have actively running jobs as indicated in JENKINS-3265

          Jose Sa added a comment - Please notice that "Reload from disk" may be unsafe if you have actively running jobs as indicated in JENKINS-3265

          wbauer added a comment -

          Same issue for me, had it with the 1.4xxx builds and now still with 1.505 - really annoying!

          wbauer added a comment - Same issue for me, had it with the 1.4xxx builds and now still with 1.505 - really annoying!

          We need to try and identify what may/may not be causing the problems. Quite a few fixes went into 1.505 and earlier but there are obviously still a few gremlins in there.

          Here's a few questions that those of you seeing the problem can try to answer:

          • are there any relevant messages in any of the Jenkins logs. Any exceptions, notices about failure to load are useful.
          • what job types do problem occur on? maven, freestyle, other.
          • are you running Jenkins direct from the war file or within tomcat/similar environment.
          • what OS are your masters/slaves running?

          Answers to those will help to point towards the right person to fix/investigate further.

          Richard Mortimer added a comment - We need to try and identify what may/may not be causing the problems. Quite a few fixes went into 1.505 and earlier but there are obviously still a few gremlins in there. Here's a few questions that those of you seeing the problem can try to answer: are there any relevant messages in any of the Jenkins logs. Any exceptions, notices about failure to load are useful. what job types do problem occur on? maven, freestyle, other. are you running Jenkins direct from the war file or within tomcat/similar environment. what OS are your masters/slaves running? Answers to those will help to point towards the right person to fix/investigate further.

          Harpreet Nain added a comment -

          Richard,

          Here are the answers as per our environment:

          1. There is nothing that we can see coming through in the logs
          2. We are using freestyle jobs
          3. The problem occurs on both i.e running direct from war file and from tomcat.
          4. We dont have a master / slave setup. We have 2 instances one on linux and and one on windows. It happens on both.

          Harpreet Nain added a comment - Richard, Here are the answers as per our environment: 1. There is nothing that we can see coming through in the logs 2. We are using freestyle jobs 3. The problem occurs on both i.e running direct from war file and from tomcat. 4. We dont have a master / slave setup. We have 2 instances one on linux and and one on windows. It happens on both.

            Unassigned Unassigned
            alex01ves Alex Vesely
            Votes:
            22 Vote for this issue
            Watchers:
            57 Start watching this issue

              Created:
              Updated:
              Resolved: