[ https://ovirt-jira.atlassian.net/browse/OVIRT-1475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=32808#comment-32808 ] eedri commented on OVIRT-1475: ------------------------------ I think the problem was that image_ng suite was talking the last successful build from Jenkins, and because most of the jobs were deleted, it took an older build instead of latest. We can't verify it because the current image_ng suite takes the squashfs image, which doesn't have a datestamp, so we can't know for sure which image was tested in the suite. I believe [~yturgema@redhat.com] is checking an option to change that to take the RPMs instead, so we'll know exactly which image was tested. So, in regards to this ticket, we need to find out why the jobs were deleted and make sure we are taking steps to prevent it happening in the future, even if we're out of space, we should probably setup long history of builds while keeping a shorter history of artifacts if possible.

Check why http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_64... wasn't time triggered for months ----------------------------------------------------------------------------------------------------------------------------

Key: OVIRT-1475 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1475 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: eedri Assignee: infra Priority: High

The follow job http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_64... is defined to run nightly (00 04 * * *) but for some reason didn't run for 9 months(!). We need to investigate why it didn't run and maybe find some clues in the logs. cc [~sbonazzo@redhat.com]

-- This message was sent by Atlassian JIRA (v1000.1085.0#100052)