[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [libmicrohttpd] Clang build fails
From: |
Tim Rühsen |
Subject: |
Re: [libmicrohttpd] Clang build fails |
Date: |
Wed, 21 Feb 2018 12:15:07 +0100 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 |
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