Well it is only partially off topic, because it is impossible to merge a db script close to release. A file rename means new CI job and that can take ages (especially for the engine and the multiple branches we have). The same what Martin is describing for the engine with FF only setup. Gating does not necessarily have to mean blocking only, it can contain an ordering component too. Martin On Mon, Nov 21, 2016 at 3:04 PM, Barak Korren <bkorren@redhat.com> wrote:
On 21 November 2016 at 13:51, Martin Sivak <msivak@redhat.com> wrote:
Will it also auto-rename the database scripts? Please please!
Well, automated systems are not supposed to make code changes without humans being aware (see other thread about "ff-only" where "rebase if necessary" is a counter-example).
What we could do is have the gate fail when colliding scripts show up (we will also have to use "ff-only" then to ensure changes are ordered). Actually this test is simple enough for "regular" CI to do, so no need to wait for the gate...
Anyway, this is not directly related to merge-gating, so a little off-topic IMO.
-- Barak Korren bkorren@redhat.com RHEV-CI Team