[ https://ovirt-jira.atlassian.net/browse/OVIRT-1475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=32836#comment-32836 ] Evgheni Dereveanchin commented on OVIRT-1475: --------------------------------------------- This job has "Max # of builds to keep" equal to 2 so all older builds are deleted by Jenkins itself. I do not see any "max-total: 2" configuration in our YAMLs so not sure when this change was introduced. Recent job config history doesn't have anything related to changes in this parameter: http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_64...

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)