-
Bug
-
Resolution: Duplicate
-
Major
-
None
-
Jenkins 2.426.3 LTS, running on Amazon Linux 2
After upgrading to 2.426.3 (from 2.426.2, I think), all our previously completed builds show up incorrectly as having a failed status, and having a start date of Dec 31, 1969. The console logs are still there, showing many of them as having completed successfully, but the history is a sea of red. At first, they showed up as being in progress, then after a service restart they show up as failed.
This looks similar to JENKINS-57726 but I'm not familiar with gatling.
- duplicates
-
JENKINS-66328 pipeline in Jenkins are showing like executed back to 1 Jan 1970
- Open
- relates to
-
JENKINS-57726 Gatling build history corrupted after upgrading to 2.178
- Open