[JIRA] (OVIRT-1475) Check why http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_64/447/ wasn't time triggered for months
Yuval Turgeman (oVirt JIRA)
jira at ovirt-jira.atlassian.net
Mon Jun 26 13:34:47 UTC 2017
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=32838#comment-32838 ]
Yuval Turgeman commented on OVIRT-1475:
---------------------------------------
There were more than 2 builds in the job's history after Sep 2016... why did it save that single job from 2016 ?
> Check why http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_64/447/ 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/447/ 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 at redhat.com]
--
This message was sent by Atlassian JIRA
(v1000.1085.0#100052)
More information about the Infra
mailing list