[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

sbonazzo (oVirt JIRA) jira at ovirt-jira.atlassian.net
Fri Jun 23 06:51:29 UTC 2017


    [ https://ovirt-jira.atlassian.net/browse/OVIRT-1475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=32800#comment-32800 ] 

sbonazzo commented on OVIRT-1475:
---------------------------------

Looks like it was running, not sure about it being working since I miss history between Job 97 and Job 448:
Success > Console Output#4​49 Jun 23, 2017 4:58 AM 
Success > Console Output#4​48 Jun 23, 2017 4:00 AM 
Success > Console Output#9​7 Sep 2, 2016 4:00 AM

It may have been failing between Sep 2, 2016 and Jun 23, 2017 but I haven't seen any failure email on infra at ovirt.org about this job

> 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