Am Sonntag, den 04.02.2018, 13:29 +0100 schrieb Bruno Haible: > Hi Tim, > > > I have CI experience with several projects and I am willing to > > help. > > Cool! > > > 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. > > Good, agree with Gitlab CI as a starter (since glibc systems are the > most important platforms to test). > > > 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. > > I think it would be better to register https://gitlab.com/gnulib as a > new > project. (In the long run, the intersection between wget maintainers > and > gnulib maintainers may be empty.) Would you be willing to do that, > please? > > "syncs+tests gnulib once a day" sounds good.
Hi Bruno, basically set up a minimalistic group and two projects. One project to build the docker images, another one to fetch gnulib and test it. The stretch CI image is already built, the testing CI still waiting to be processed. Meanwhile you should create a Gitlab account and tell me your nick. So I can invite you and give you the appropriate permissions. There is much to be tuned (permissions, build optimizations, different kind of builds/tests e.g. with/without sanitizers). And there is much to learn about the Gitlab UI. Maybe it's better to discuss those details via PM - feel free to contact me. Regards, Tim