Re: Coverity scans?

2019-08-01 Thread Tim Düsterhus
Dinko, Am 01.08.19 um 12:20 schrieb Dinko Korunic: > Haproxy Coverity project token is: *snip* > Given that it’s per-project token, that can be hardcoded in TravisCI > configuration without any issues. I'm not sure if the token is meant to kept secret, but I wanted to let you know that you sent

Re: Coverity scans?

2019-08-01 Thread Илья Шипицин
чт, 1 авг. 2019 г. в 15:23, Dinko Korunic : > Hi Илья, > > Haproxy Coverity project token is: 9Zw8bB4a > Given that it’s per-project token, that can be hardcoded in TravisCI > configuration without any issues. > > In regards to notification mails, well for now I think that can have your > and my

Re: Coverity scans?

2019-08-01 Thread Dinko Korunic
Hi Илья, Haproxy Coverity project token is: 9Zw8bB4a Given that it’s per-project token, that can be hardcoded in TravisCI configuration without any issues. In regards to notification mails, well for now I think that can have your and my mail for now until we think of something better. Willy,

Re: Coverity scans?

2019-08-01 Thread Илья Шипицин
also, I've no idea what to specify in COVERITY_SCAN_NOTIFICATION_EMAIL (which is mandatory) чт, 1 авг. 2019 г. в 12:32, Dinko Korunic : > Hey Илья, > > Looks fine and clean. I guess that we would use existing project name > (Haproxy) or you would like to continue with your own? > > Last, I

Re: Coverity scans?

2019-08-01 Thread Илья Шипицин
чт, 1 авг. 2019 г. в 12:32, Dinko Korunic : > Hey Илья, > > Looks fine and clean. I guess that we would use existing project name > (Haproxy) or you would like to continue with your own? > I would move to "haproxy/haproxy" however, proper token must be set in travis-ci environment (if token is

Re: Coverity scans?

2019-08-01 Thread Dinko Korunic
Hey Илья, Looks fine and clean. I guess that we would use existing project name (Haproxy) or you would like to continue with your own? Last, I wonder do we really need verbose (V=1) builds and do you think if they make sense for Coverity builds? Thanks, D. > On 30 Jul 2019, at 10:35, Илья

Re: Coverity scans?

2019-07-30 Thread Илья Шипицин
Dinko, please have a look https://github.com/chipitsine/haproxy/blob/coverity/.travis.yml#L37-L45 what do you think (if we will move that to https://github.com/haproxy/haproxy) ? ср, 17 июл. 2019 г. в 16:36, Dinko Korunic : > Dear Илья, > > I’ve increased your access level to

Re: Coverity scans?

2019-07-21 Thread Илья Шипицин
ср, 17 июл. 2019 г. в 16:36, Dinko Korunic : > Dear Илья, > > I’ve increased your access level to Contributor/Member. I terms of > Travis-CI scans, there are some catch22s with current Coverity suite as it > is compiled against ancient glibc and ancient kernel headers and > requires

Re: Coverity scans?

2019-07-17 Thread Dinko Korunic
Dear Илья, I’ve increased your access level to Contributor/Member. I terms of Travis-CI scans, there are some catch22s with current Coverity suite as it is compiled against ancient glibc and ancient kernel headers and requires vsyscall=emulate kernel boot option to properly work — not sure if

Re: Coverity scans?

2019-07-17 Thread Илья Шипицин
Hello, yep, contributor/member would be nice. Also, I can setup automated travis-ci scans On Wed, Jul 17, 2019, 3:27 PM Dinko Korunic wrote: > Hey Илья, > > Let me know if you would like Contributor/Member role for your account on > Haproxy Coverity account. I was initially more involved and I

Re: Coverity scans?

2019-07-17 Thread Dinko Korunic
Hey Илья, Let me know if you would like Contributor/Member role for your account on Haproxy Coverity account. I was initially more involved and I have started configuring modules and parts of code blocks into coherent units, but stopped at some point due to lack of time and interest. There