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