[
https://ovirt-jira.atlassian.net/browse/OVIRT-251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
eyal edri [Administrator] updated OVIRT-251:
--------------------------------------------
Resolution: Done
Status: Closed (was: New)
not relevant anymore with STD CI.
There is another ticket in general to create a pipeline of tests, this is in
the hands of developers now, as all the code is in check-patch/check-merged and
it can be modified to run as a chain if needed.
> 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
(v1000.5.0#72002)
_______________________________________________
Infra mailing list
[email protected]
http://lists.ovirt.org/mailman/listinfo/infra
