Am Sonntag, den 04.02.2018, 11:20 +0100 schrieb Bruno Haible: > Hi all, > > If you are familiar with Travis CI or Appveyor CI, please help > keeping gnulib > at a high quality! > > It is normal for a developer to push a buggy commit by mistake. But > it should > not be normal that such a mistake, that leads to a test failure on > standard > glibc systems, remains unnoticed for 10 days. > > It would be good to have a continuous integration (Travis or > Appveyor, I > don't mind) of gnulib, to detect test failures early. > > There is already a github mirror of the gnulib git repo, at > https://github.com/coreutils/gnulib, and it is apparently kept up-to- > date > automatically. > > The continuous integration should probably run these commands: > $ ./gnulib-tool --create-testdir --dir=/some/testdir --single- > configure \ > --with-c++-tests --without-privileged-tests > $ cd /some/testdir > $ make > $ make check
Hi Bruno, I have CI experience with several projects and I am willing to help. >From my experience and knowledge, the Gitlab CI is much more configurable than e.g. Travis. It is docker based and thus limited to all kinds of Linux variants (including cross-platform builds, e.g. MinGW). Therefore I use Travis for OSX testing only. I have no experience with AppVeyor wich would be useful for native Windows testing. As a starter, I could set up a gnulib test CI as a subproject in https: //gitlab.com/gnuwget that syncs+tests gnulib e.g. once a day. WDYT ? Regards, Tim
