[
https://ovirt-jira.atlassian.net/browse/OVIRT-1475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=32807#comment-32807
]
eedri commented on OVIRT-1475:
------------------------------
It looks like the job was running all the time ( full logs can be found on the
Jenkins server, under /var/log/jenkins), here is the log from this month [1].
[~ederevea] is it possible the jobs were deleted from Jenkins during the latest
space cleanup?
[1]
jenkins.log-20170601.gz:INFO: ovirt-node-ng_master_build-artifacts-el7-x86_64
#425 main build action completed: SUCCESS
jenkins.log-20170602.gz:INFO: ovirt-node-ng_master_build-artifacts-el7-x86_64
#426 main build action completed: SUCCESS
jenkins.log-20170603.gz:INFO: ovirt-node-ng_master_build-artifacts-el7-x86_64
#427 main build action completed: SUCCESS
jenkins.log-20170605.gz:INFO: ovirt-node-ng_master_build-artifacts-el7-x86_64
#429 main build action completed: SUCCESS
jenkins.log-20170606.gz:INFO: ovirt-node-ng_master_build-artifacts-el7-x86_64
#430 main build action completed: SUCCESS
jenkins.log-20170607.gz:INFO: ovirt-node-ng_master_build-artifacts-el7-x86_64
#431 main build action completed: SUCCESS
jenkins.log-20170608.gz:INFO: ovirt-node-ng_master_build-artifacts-el7-x86_64
#432 main build action completed: SUCCESS
jenkins.log-20170609.gz:INFO: ovirt-node-ng_master_build-artifacts-el7-x86_64
#433 main build action completed: SUCCESS
jenkins.log-20170610.gz:INFO: ovirt-node-ng_master_build-artifacts-el7-x86_64
#434 main build action completed: SUCCESS
jenkins.log-20170612.gz:INFO: ovirt-node-ng_master_build-artifacts-el7-x86_64
#436 main build action completed: SUCCESS
jenkins.log-20170613.gz:INFO: ovirt-node-ng_master_build-artifacts-el7-x86_64
#437 main build action completed: SUCCESS
jenkins.log-20170614.gz:INFO: ovirt-node-ng_master_build-artifacts-el7-x86_64
#438 main build action completed: SUCCESS
jenkins.log-20170615.gz:INFO: ovirt-node-ng_master_build-artifacts-el7-x86_64
#439 main build action completed: SUCCESS
jenkins.log-20170616.gz:INFO: ovirt-node-ng_master_build-artifacts-el7-x86_64
#440 main build action completed: SUCCESS
jenkins.log-20170617.gz:INFO: ovirt-node-ng_master_build-artifacts-el7-x86_64
#441 main build action completed: SUCCESS
jenkins.log-20170619.gz:INFO: ovirt-node-ng_master_build-artifacts-el7-x86_64
#443 main build action completed: SUCCESS
jenkins.log-20170620.gz:INFO: ovirt-node-ng_master_build-artifacts-el7-x86_64
#444 main build action completed: SUCCESS
jenkins.log-20170621.gz:INFO: ovirt-node-ng_master_build-artifacts-el7-x86_64
#445 main build action completed: SUCCESS
jenkins.log-20170623.gz:INFO: ovirt-node-ng_master_build-artifacts-el7-x86_64
#447 main build action completed: SUCCESS
jenkins.log-20170624.gz:INFO: ovirt-node-ng_master_build-artifacts-el7-x86_64
#448 main build action completed: SUCCESS
jenkins.log-20170624.gz:INFO: ovirt-node-ng_master_build-artifacts-el7-x86_64
#449 main build action completed: SUCCESS
cc [[email protected]]
> 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 [[email protected]]
--
This message was sent by Atlassian JIRA
(v1000.1085.0#100052)
_______________________________________________
Infra mailing list
[email protected]
http://lists.ovirt.org/mailman/listinfo/infra
