2017-12-15 13:07 GMT+05:00 Aleksandar Lazic <al-hapr...@none.at>: > Hi > > ------ Originalnachricht ------ > Von: "Илья Шипицин" <chipits...@gmail.com> > An: "Aleksandar Lazic" <al-hapr...@none.at> > Cc: "Olivier Doucet" <webmas...@ajeux.com>; "HAProxy" < > haproxy@formilux.org> > Gesendet: 14.12.2017 14:57:29 > Betreff: Re: CI/CD HAProxy > > >> >> 2017-09-16 20:01 GMT+05:00 Aleksandar Lazic <al-hapr...@none.at>: >> >>> Hi Olivie. >>> >>> Olivier Doucet wrote on 15.09.2017: >>> >>> > Hi, >>> > >>> > I wanted to open a new thread, as "cppcheck finding" was hijacked with >>> this CICD / testing ;) >>> >>> +1 >>> >>> > I think the best is the enemy of the good : why not start with a few >>> > easy tests ? For example just a mix of tiny / big config files to test >>> the parser. >>> > >>> > I understand the difficult part of the test is to setup complicated >>> > infrastructures with many softwares to test edge cases, but that can >>> be done later. >>> > >>> > Willy, there is no need to setup and maintain a buildfarm (no one has >>> > time for this) : as this is an open project, we can use platform like >>> > Travis-CI : all tests are described in a yaml file incorporated in the >>> > project. It works out of the box for any project hosted at github. We >>> can use a mirror for this. >>> >>> I like the idea. >>> >>> Does anyone know who own https://github.com/haproxy/haproxy < >>> https://github.com/haproxy/haproxy> ? >>> >>> I can start with some easy checks, the question is should we have a git >>> hook when a commit is done on http://git.haproxy.org ? >>> >>> > What is great about these is that you can easily plug syntax check >>> softwares ;) >>> >>> +1 ;-) >>> >>> > Olivier >>> >>> -- >>> Best Regards >>> Aleks >>> >>> >>> >> >> Hello, >> >> I made weird thing >> >> >> https://gitlab.com/chipitsine/haproxy/blob/master/.gitlab-ci.yml >> >> repo itself is merged hourly with upstream repo (by using external syncer) >> >> https://gitlab.com/chipitsine/haproxy/-/jobs >> > > I can't read it, is it a public repo? >
I set it to "internal", that means any authenticated user can access it probably, I can make repo itself public, but pipelines are not available publicly > > Best regards > aleks > >
