чт, 18 апр. 2019 г. в 21:51, Илья Шипицин <[email protected]>:
> > > чт, 18 апр. 2019 г. в 21:45, Willy Tarreau <[email protected]>: > >> Hi Ilya, >> >> On Wed, Apr 17, 2019 at 01:06:11PM +0500, ???? ??????? wrote: >> > btw, we can run lua tests >> > >> > https://travis-ci.com/chipitsine/haproxy-1/builds/108641032 >> > >> > so... how do we want to run lua ? always enabled ? or two builds (with >> and >> > without lua) ? >> >> I'd say that we generally detect more problems by having lots of features >> than few features. However it's true that build issues are often >> discovered >> when features are disabled precisely because developers tend to enable >> lots >> of them to cover a wide range of issues. >> >> Thus at first enabling it would possibly be better. Later if you figure >> it's cheap to run multiple builds, it might make sense to have two builds, >> or even try to randomly mix certain options. Another thing that regularly >> breaks is openssl-derivatives like LibreSSL and BoringSSL. I'm just not >> convinced there are enough users to warrant extra tests at the moment >> though. >> > > I planned to add various openssl versions like 1.0.1, 1.0.2, 1.0.0, 1.1.1, > ... > I think we can add libressl, boringssl as well. > > > >> >> I've merged your patch in its current state hoping it will help, but >> I still have zero idea about how to use it, so please send some doc >> ASAP. >> > > also travis-ci must be enabled on github project, > please follow this guide > https://docs.travis-ci.com/user/tutorial#to-get-started-with-travis-ci > I mean the following steps (after that builds will run on every commit) - Go to Travis-ci.com <https://travis-ci.com> and *Sign up with GitHub* <https://travis-ci.com/signin>. - Accept the Authorization of Travis CI. You’ll be redirected to GitHub. - Click the green *Activate* button, and select the repositories you want to use with Travis CI. > > > >> >> Thanks, >> Willy >> >
