Re: automated CI testing

[Tim Rühsen]

On Mittwoch, 17. Mai 2017 19:09:52 CEST Bruno Haible wrote:
> Hi Tim,
> 
> > What about automated / CI testing ?
> > We (the Wget maintainers) recently set up a group 'gnuwget' on Gitlab
> > with CI runners (Debian, CentOS, Fedora). I could add gnulib as a
> > project so that it can use these runners as well. The only thing to do
> > for the gnulib project is to add a .gitlab-ci.yml file for building and
> > testing (gcc, clang, valgrind, coverage reporting, ...).
> 
> Simon had an autobuild site [1][2], but it appears to be offline now.
> 
> From my perspective, glibc systems are the ones which pose the least
> problems, and get reported quickly anyway. Therefore what is more valuable
> for gnulib (IMO) is automated testing on 20 different platforms.

Of course everybody wishes to have a CI for 20 different platform :-)

But you have to start at some point, picking the low hanging fruits. And that 
is Gitlab CI based on Docker. You can build, test and deploy with using 
different Linux platforms (x86, amd64, different software release 
environments). Also cross-platform builds can be done (ARM, MinGW, ...), 
that's up to you. You can have a free OSX test environment using Travis CI - 
that needs a mirror on Github. There is AppVeyor for Windows CI, but I have no 
experience with that.
And there is the OpenCSW Solaris build platform...

For real VMs with other OSes running, you can
- set up your own VMs 'at home'
- pay for customizable VMs and CPU power
- find a sponsor to pay for VMs and CPU power

> Bruno
> 
> [1]
> https://www.gnu.org/software/gnulib/manual/html_node/Build-robot-for-gnulib
> .html [2] http://josefsson.org/autobuild/

With Best Regards, Tim

signature.asc
Description: This is a digitally signed message part.