On Tue, 11 Dec 2018 13:06:36 -0800, Ben Pfaff <b...@ovn.org> wrote: > On Tue, Dec 11, 2018 at 05:34:17PM +0300, Ilya Maximets wrote: >> CirrusCI [1] is free for open-sorce projects and provides similar >> to TravisCI interfaces. One significant difference is ability >> to run tasks on FreeBSD instances. >> >> This patch adds simple configuration file to test OVS build >> on two FreeBSD releases with gcc and clang. >> Unit tests are commented out because they are broken for now. >> >> To enable the automated checks Cirrus CI application from GitHub >> Marketplace should be installed. See details in Quick Start guide [2]. >> >> [1] https://cirrus-ci.org >> [2] https://cirrus-ci.org/guide/quick-start/ >> >> Signed-off-by: Ilya Maximets <i.maxim...@samsung.com> >> --- >> >> This could be useful to test FreeBSD build automatically to early >> detect issues. CirrusCI looks suitable for that purpose and it's >> the only public CI system that I managed to find that supports >> FreeBSD images. Sending as RFC to start discussion. >> >> Few more differentiation points with Travis. Cirrus allows to >> configure number of CPUs and the amount of required memory. It >> also supports Linux, OSX and Windows containers. So, maybe, if >> we'll like it, we could drop Travis and AppVeyor and use single >> CI system for all the tests. >> >> I'm not advertising and not trying to convince to replace our >> current CI systems. I found CirrusCI just few days ago by a mail [3] >> in qemu-devel list. I just think that it's the only option for >> now to test BSD builds with public CI. And it worked fine for me >> with below configuration. >> >> Thoughts ? >> >> As a note: I just spotted that TravisCI adds windows support. >> Maybe we could use it in the future for windows builds. >> >> [3] https://lists.nongnu.org/archive/html/qemu-devel/2018-12/msg00935.html > > Good idea. It's hard for me to see what harm this would cause, so I > enabled cirrus-ci at github and applied this to master.
FYI, I've also enabled the cirrus-ci under the ovsrobot, in tandem. > The big weakness with appveyor is that its limits are too low to run the > whole OVS testsuite. I wonder whether cirrus-ci has better limits for > this purpose. _______________________________________________ dev mailing list d...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-dev
