----- Original Message ----- > From: "Antoni Segura Puimedon" <[email protected]> > To: [email protected] > Sent: Friday, June 6, 2014 5:44:40 PM > Subject: Travis-ci for continuous integration > > Hi, > > Vinzenz Feenstra today showed me how easy it is to integrate travis continous > integration building with github repositories and pointed out that it is > free for floss projects. > > Since we are a floss project and have already mirrors in github, I would > propose > that we create .travis.yml files so some of our continuous integration tests > and builds run (without spending any of our resources) in travis. > > The big advantage for vdsm, for example, is that the travis containers run > debian and it would be very nice to have it set up so it alerts us if we > break the debian/ubuntu builds.
would be interesting to check what kind of service you get there, it's appealing since it's hosted and doesn't require us to manage another CI server, and we get free resources on the way, but need to see exactly what is process of using and how much overhead it will add to infra maintenance. we're planning indeed to add ubunto/debian slaves on jenkins.ovirt.org, it was delayed due to infra problems with current providers (os1 for example), and the new lab that is in progress, so hopefully we'll get ubunto slaves up and running soon. eyal. > _______________________________________________ > Infra mailing list > [email protected] > http://lists.ovirt.org/mailman/listinfo/infra > _______________________________________________ Infra mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/infra
