Description of problem: We need to backport the automation scripts to the ovirt-3.5 stable branch. This is safe -no code change involved at all-, and we can reuse all the work done on more modern branches. This bug is to track this operation Version-Release number of selected component (if applicable): 4.16.27 How reproducible: 100% Steps to Reproduce: 1. submit a patch to gerrit, targeting ovirt-3.5 branch Actual results: No automated CI sanity checks and tests run Expected results: Automated CI sanity checks and tests should run
priority high, severity low: this doesn't directly impact any customer. However, it greatly helps the maintainership effort
Francesco, why not targeting to ovirt-engine-3.5.6 (and not 3.5.7?)
(In reply to Oved Ourfali from comment #2) > Francesco, why not targeting to ovirt-engine-3.5.6 (and not 3.5.7?) No reason, actually the earlier is in, the better. Changed. Please note that there is no 4.16.x version available in "target release" dropdown menu, so I can't set it.
Will it be in on time (gonna be built on Tuesday)?
(In reply to Oved Ourfali from comment #4) > Will it be in on time (gonna be built on Tuesday)? The status is better than it could look at first glance. Most patches are on track and near to merge; quite some of them don't affect production code, because they are about either tests or automation scripts. It seems we are stuck because the automation script complain about missing target releases for stable branch; this is in turn caused by the lack of suitable options in the "target release" drop down menu on BZ. We need to fill some future target releases (4.16.27...28...29...30...).
all relevant patches merged -> MODIFIED. We can enable the job on jenkisns side and see.
Francesco, Does any QE verification needed on this?
(In reply to Gil Klein from comment #7) > Francesco, Does any QE verification needed on this? I'd say no. All the changes we backported are either on automation scripts (= no production code changed at all) or in the test code, which is exercised each time tests are runned. Can't think of any production code change.
(In reply to Francesco Romani from comment #8) > (In reply to Gil Klein from comment #7) > > Francesco, Does any QE verification needed on this? > > I'd say no. All the changes we backported are either on automation scripts > (= no production code changed at all) or in the test code, which is > exercised each time tests are runned. Can't think of any production code > change. Thus CodeChange, P.
oVirt 3.5.6 has been released and the bz verified, moving to closed current release.