Thoughts about Travis-CI integration

[Alexander Todorov]

Hi folks,
this message sparked an interest:
https://lists.fedorahosted.org/pipermail/python-bugzilla/2013-December/000200.html

In addition to that I've inspected around 30 packages which seem to be missing 
an upstream test suite (a few have one but it is not automatically executed in 
%check section in the spec file).

I'm pretty sure many more packages are like this, I just didn't have the time to 
investigate all several thousands of them.


My idea is simple - starting after the holidays to call for help in writing test 
suites (or more test cases) for packages. This can be coupled with settings to 
execute them in Travis CI or another CI system of choice.



My questions are:

* What is the general feeling of using Travis CI in Fedora? It is well 
established in Ruby and Python circles but I know we like to keep dependency on 
external services to minumum.

Does Fedora have its own CI infrastructure coupled with Koji ?

Maybe deploy our own instance or contribute to Travis with a pool of systems 
sponsored by Fedora?

What to do with packages whose test suite is not suitable to be executed during 
build (e.g. due to requirements or limitations on the build servers) ?

What's your take ?

( Adding Tim Flink to CC to answer from the infrastructure side. )


* Are there any volunteers to join me in planning and coordinating this project? 
We need to somehow prioritize which packages need inspection and working on, 
count the available test cases, report bugs if missing, produce patches, etc. It 
will be a long run one and needs lots of work just because the great number of 
packages.


* Who else should I be talking to ?


Regards,
Alex
--
http://atodorov.org