On Sun, Sep 4, 2016 at 6:55 PM, Eyal Edri <ee...@redhat.com> wrote: > Any reason to keep running db upgrade jobs? [1] while we already have engine > setup+upgrade jobs running per patch? [2]
IMO [2] is enough. In the not-very-common event that engine-setup breaks not due to dbscripts, we should fix it quickly anyway. Downside of [1] is mainly extra maintenance on your (CI) side. If you keep it, you might soon need to patch it again to support [3]. [3] https://bugzilla.redhat.com/show_bug.cgi?id=1366900 > > > [1] > http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-db-from-master_el7_created/ > [2] > http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-4.0_el7_created/ > > > -- > Eyal Edri > Associate Manager > RHV DevOps > EMEA ENG Virtualization R&D > Red Hat Israel > > phone: +972-9-7692018 > irc: eedri (on #tlv #rhev-dev #rhev-integ) > > _______________________________________________ > Devel mailing list > Devel@ovirt.org > http://lists.ovirt.org/mailman/listinfo/devel -- Didi _______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel