[
https://ovirt-jira.atlassian.net/browse/OVIRT-1475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=32809#comment-32809
]
Yuval Turgeman commented on OVIRT-1475:
---------------------------------------
Yes, [~eedri] is right, I think the deletion messed up lastSuccessful, making
it point to some old version. However, using the rpm would mean a bigger
change, and it would take a little more time to run (extract the rpm etc). I
think that the best way to fix this, is to copy the squashfs from its original
place to the exported-artifacts dir with a timestamp, so instead of cp
<squashfs> exported-artifacts, it would be something like cp squashfs
exported-artifacts/squashfs-<builddate>, and let image-ng continue to pick up
the squashfs by a build number.
> 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
