+1
that's great news!
this will help us keep both engine-setup and engine-upgrade stable and detect regressions
in spec files or any other misc packaging issues.
in the per patch job we should limit the job to run only on changed in 'packging'
and 'db-scripts' dir,
so it won't run on non-related changes.
kudos for the effort on ci & engine bug fixes.
Eyal.
----- Original Message -----
From: "Kiril Nesenko" <kiril(a)redhat.com>
To: "infra" <infra(a)ovirt.org>
Sent: Tuesday, June 4, 2013 3:21:27 PM
Subject: engine upgrade job
Hello,
Finally after few real bugs in upgrade flow upgrade job is green ! [1].
Creating a new job that will perform upgrade per patch.
[1]
http://jenkins.ovirt.org/job/ovirt_engine_upgrade_stable_32_to_latest_32/...
- Kiril
_______________________________________________
Infra mailing list
Infra(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra