On 02/21/2018 10:28 AM, Christian Grothoff wrote: > Hi, > > Build issue should be fixed in Git now.
Thanks ! > IIRC, our CI (Buildbot) is not (yet) setup to build with clang, but also > it doesn't send out proper notifications on failures in the first place, > so it is right now of limited use. > > Help with setting up better CIs would always be welcome, albeit I > personally prefer using our "own" infrastructure (we have machines) > instead of depending on some corporate hosting. Well yes, I don't have the luxury of an own infrastructure... > Generally, I would like > to end up with a setup where the entire CI configuration is also in a > Git repo and can be easily collaboratively improved. So if you have time > and energy to make that happen, great ;-) Gitlab allows exactly that, but you have your own CI already running and the missing parts are maybe just a piece of configuration. So it has to be your initiative. If you like to give Gitlab a chance, let me know and I surely can help. You can also have your own Gitlab instance without gitlab.com involved. And BTW, you can use gitlab-ci-multi-runner to use your own machines / OSes as CI runners. The gitlab.com CI hosting is limited to docker, but hey - it's free to use. And since the CI setup is developed in a git repo as well, nothing is lost, even if gitlab.com dies. With Best Regards, Tim
signature.asc
Description: OpenPGP digital signature