Willy,

I'll chime in here.

Am 23.04.19 um 11:16 schrieb Willy Tarreau:
> On Mon, Apr 22, 2019 at 10:13:52PM +0500, ???? ??????? wrote:
>> I can enable travis-ci by myself if you can temporarily grant me an access
>> to github repo
> 
> I'm not against doing this, it's just that I still have no idea what
> the impacts are. In short, will any of us get any extra work once this
> is enabled ? Does someone have to manage this once in a while ? Will it

No real management necessary. You might need to update the Travis
configuration every once in a while if you want to add additional build
options or something about the reg test invocations change. The syntax
is self explanatory I guess.

> slow down git push ? Will someone get spammed with e-mails, and if so,

The git push is not affected. Travis runs entirely asynchronous and
reports the build back to GitHub and ...

... optionally via email if the build starts to fail (either because
HAProxy fails to compile or because reg-tests fail). These email
notifications can be updated / disabled in .travis.yml. See here for
details:

https://docs.travis-ci.com/user/notifications#configuring-email-notifications

> whom ? All this might possibly be acceptable in exchange for better
> testing, it's just that for me it's totally obscure and I have no idea
> what we're engaging in by doing it. I just want to make sure we're not
> going to rush a revert because it adds some unplanned burden to anyone
> that nobody initially expected. The team of people having their hands
> dirty on tools is small and I really want to be sure we're not going to
> give them extra work (at least without their approval).
> 
> So if you can explain in a few words what will happen once you enable
> this, that would be great ;-)

Ideally you should not notice anything: It means no one commited bad
code. It might need some adjustments in the beginning, very similar to
the issue tracker :-)

Currently it builds only with clang on Linux with a bunch of options
enabled. I have a version with additional gcc on Linux, clang on Mac and
no build options. Unfortunately it fails the build:
https://github.com/TimWolla/haproxy/commit/32b32f5fad0c45a14b7f1a300d811430f10391c2
and https://travis-ci.com/TimWolla/haproxy/builds/108870403

I'll have to investigate that and then provide the improved version with
a patch. But for the start the current one by Ilya is absolutely
sufficient and a good improvement over the current situation.

Best regards
Tim Düsterhus

Reply via email to