On Sat, Jul 19, 2014 at 12:23 PM, Reinhard Tartler <[email protected]> wrote: > On Sat, Jul 19, 2014 at 11:44 AM, Marc-Antoine ARNAUD > <[email protected]> wrote: >> Hi, >> >> Someone have already tested Travis with LibAV ? >> We using on projects, and it was very helpfull. >> >> I already try to setup the configuration file >> <https://github.com/MarcAntoine-Arnaud/libav/blob/17bc81dff985591e15fd68ce22e0b18def3aab8b/.travis.yml> >> but it requires to be present on the code repository. >> The Travis CI can build under Ubuntu, but also on MacOS platform. >> >> If you're okay, I can setup the configuration. > > For master, I believe that it would be kindof redundant to our > existing FATE farm. Or am I missing something? > > For release branches, we currently don't have any FATE Farm. It would > be great to have something like that, but as far as I understand, it > is a lot of effort to setup FATE for release branches, which is really > a shame. > > Would it be possible to setup travis in a way to verify that the Libav > release branches build on both Linux and on MacOS? Is it possible to > access the binaries produced by such builds?
To answer my own question: I have setup travis to build our release/10 branch: https://travis-ci.org/siretart/libav As you can see, access to the internet seems to be available. The build machine is an amd64 bit ubuntu 12.04 LTS host, and we can install arbitrary packages. I have not explored MacOS builds yet. Also, it seems not to be possible to access the build workspace directly. Maybe the build could upload binaries somewhere, but it is currently unclear to me how we would authenticate/validate such builds. Integrating a dedicated Mac Builder for release binaries into our jenkins setup seems favorable. -- regards, Reinhard _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
