This ticket can be closed, as we move to minikube which does not require an image build anymore.

@Fabian Deutsch we now support GitHub projects in standard CI and we can also build docker images, so if its still relevant,
we can help with it, there are already example of how to add new GitHub projects here [1]

[1] http://ovirt-infra-docs.readthedocs.io/en/latest/CI/Github_Integration/index.html

Is this task still relevant? @Eyal Edri

Well, there is a big conceptual difference between '.travisci' and 'automation'. While '.travisci' was designed as just the signalling interface for the Travis system. 'automation' was designed to generalize the interface of build systems, so that a generic, isolating, dependency-resolving build system could be created. It was always a goal to also allow running the build/test process locally. In that sense 'automation' is considered as inseparable from the code as its 'Makefile'.

.ovirtci as a directory would also work.

To me it is a benefit to have the "namespaced" / "branded" ci files, as it gives the files a context, an dthe reader a hint of where they are getting executed.

I also do favor the fact that it's hidden, because after all, the CI is crucial, but it's not a part of the code - it is there to smoke test the code.