Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

chain ovirt-engine merge jobs

Description

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.

Activity

Show:

Eyal Edri April 27, 2016 at 9:07 AM

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.

Eyal Edri April 13, 2016 at 6:55 PM

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.

Former user March 21, 2016 at 10:49 AM
Edited

That's 40

Former user March 21, 2016 at 10:49 AM
Edited

ovirt-engine_3.6_style_gerrit
ovirt-engine_master_style_gerrit
ovirt-engine_3.5_find-bugs_merged
ovirt-engine_3.6_find-bugs_gerrit
ovirt-engine_3.6_find-bugs_merged
ovirt-engine_3.5_unit_tests_gerrit
ovirt-engine_3.6_unit-tests_gerrit
ovirt-engine_3.6_unit-tests_merged
ovirt-engine_master_find-bugs_gerrit
ovirt-engine_master_find-bugs_merged
ovirt-engine_master_unit-tests_gerrit
ovirt-engine_master_unit-tests_merged
ovirt-engine_3.5_dao-unit-tests_gerrit
ovirt-engine_3.6_dao-unit-tests_merged
ovirt-engine_3.6_dao-unit-tests_created
ovirt-engine_3.6_scan-open-tasks_merged
ovirt-engine_3.6_purge-maven-repo_merged
ovirt-engine_master_dao-unit-tests_merged
ovirt-engine_master_find-bugs_gerrit_juan
ovirt-engine_3.5_compile_checkstyle_gerrit
ovirt-engine_master_dao-unit-tests_created
ovirt-engine_master_scan-open-tasks_merged
ovirt-engine_3.6_upgrade-from-3.5_el6_merged
ovirt-engine_3.6_upgrade-from-3.6_el6_merged
ovirt-engine_master_coverity-analysis_merged
ovirt-engine_3.6_upgrade-db-from-3.5_el6_merged
ovirt-engine_3.6_upgrade-db-from-3.6_el6_merged
ovirt-engine_master_upgrade-from-3.6_el7_merged
ovirt-engine_3.6_upgrade-db-from-3.5_el6_created
ovirt-engine_3.6_upgrade-db-from-3.6_el6_created
ovirt-engine_3.6.4_upgrade-db-from-3.5_el6_merged
ovirt-engine_3.6.4_upgrade-db-from-3.6_el6_merged
ovirt-engine_3.6.4_upgrade-db-from-3.5_el6_created
ovirt-engine_3.6.4_upgrade-db-from-3.6_el6_created
ovirt-engine_master_upgrade-db-from-3.6_el7_merged
ovirt-engine_master_upgrade-from-master_el7_merged
ovirt-engine_master_upgrade-db-from-3.6_el7_created
ovirt-engine_master_upgrade-db-from-master_el7_merged
ovirt-engine_master_upgrade-db-from-master_el7_created
ovirt-engine_master_upgrade-from-3.6_el7_merged_test_puppet_ngoldin

Eyal Edri March 21, 2016 at 9:57 AM

How many jobs we still have that are not using standard ci? I guess a lot were dropped with 3.5.

Former user March 21, 2016 at 9:34 AM

What we have to do here is to merge them into the standard ci, and stop having multiple jobs out of it

Eyal Edri March 15, 2016 at 8:06 AM

is this relevant also for 3.6 with standard ci?

Done

Details

Assignee

Reporter

Components

Parent

Created August 27, 2014 at 11:40 AM
Updated May 25, 2017 at 11:30 AM
Resolved April 27, 2016 at 9:07 AM