[ https://ovirt-jira.atlassian.net/browse/OVIRT-251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14828#comment-14828 ] eyal edri [Administrator] commented on OVIRT-251: ------------------------------------------------- Will this still be relevant in STD CI? We don't have too much jobs left outside of it for ovirt-engine, and we're planning to remove/replace existing ones.

chain ovirt-engine merge jobs -----------------------------

Key: OVIRT-251 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-251 Project: oVirt - virtualization made easy Issue Type: New Feature Components: Jenkins Affects Versions: Test Reporter: sbonazzo Assignee: infra

Currently a merge event triggers: \\- http://jenkins.ovirt.org/job/ovirt-engine_3.5_upgrade-from-3.4_merged \\- http://jenkins.ovirt.org/job/ovirt-engine_3.5_create-rpms_merged \\- http://jenkins.ovirt.org/job/ovirt-engine_3.5_find-bugs_merged All of them performs builds at different stages. I suggest to run first \\- http://jenkins.ovirt.org/job/ovirt-engine_3.5_find-bugs_merged and if it finish with success, I suggest to use rpms built from \\- http://jenkins.ovirt.org/job/ovirt-engine_3.5_create-rpms_merged for running: \\- http://jenkins.ovirt.org/job/ovirt-engine_3.5_upgrade-from-3.4_merged otherwise abort the chain as soon as it fails. This will reduce the times we rebuild the same code and the slaves load.

-- This message was sent by Atlassian JIRA (v7.2.0-OD-05-030#72002)