-
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
-
[JENKINS-72659] Build history corrupted after updating to 2.426.3 (LTS)
Link | New: This issue relates to JENKINS-57726 [ JENKINS-57726 ] |
Description | Original: 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. |
New:
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 https://issues.jenkins.io/browse/JENKINS-57726 but I'm not familiar with gatling. |
Description |
Original:
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 https://issues.jenkins.io/browse/JENKINS-57726 but I'm not familiar with gatling. |
New:
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 but I'm not familiar with gatling. |
Description |
Original:
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 but I'm not familiar with gatling. |
New:
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|https://issues.jenkins.io/browse/JENKINS-57726] but I'm not familiar with gatling. |
Link | New: This issue is related to JENKINS-66328 [ JENKINS-66328 ] |
Resolution | New: Duplicate [ 3 ] | |
Status | Original: Open [ 1 ] | New: Closed [ 6 ] |
Link | New: This issue duplicates JENKINS-66328 [ JENKINS-66328 ] |
Link | Original: This issue is related to JENKINS-66328 [ JENKINS-66328 ] |