[master] e7d624664 First stab at getting coverity running

[Dridi Boukelmoune]

On Thu, Mar 14, 2019 at 11:13 PM Federico G. Schwindt <fgsch at lodoss.net> wrote:
>
>
> commit e7d6246645ba316ac05cc0e5abc9b2e68ba71587
> Author: Federico G. Schwindt <fgsch at lodoss.net>
> Date:   Thu Mar 14 22:08:52 2019 +0000
>
>     First stab at getting coverity running

Back when I introduced Coverity Scan support in cashpack I managed to
contain the complexity:

https://github.com/Dridi/cashpack/blob/master/.travis.yml#L50-L57

The ugly part was that 1) I triggered those on demand by pushing
master to a dedicated "coverity_scan" branch and 2) since I have a
plethora of jobs in my matrix I wanted to make sure the coverity build
happened only once:

https://github.com/Dridi/cashpack/blob/master/.travis.yml#L58-L59

And I think it's an opportunity to have a travis/ subdirectory in our
tools/ directory to offload some of the yaml file complexity to
external scripts. It worked like a charm for me with vmod-querystring:

https://github.com/Dridi/libvmod-querystring/blob/master/.travis.yml#L59-L61
https://github.com/Dridi/libvmod-querystring/tree/master/travis

If I needed to redo it today, I would use a Travis cron build instead
of a dedicated branch. The mechanic to detect whether it's a cron
job or a dedicated branch is basically the same: inspect your
environment.

I do this to run weekly CI against master instead of my minimum
required version:

https://github.com/Dridi/libvmod-querystring/blob/master/travis/install_varnish.sh

And that's how I'm informed when something lands in master and
breaks downstream. (VRT, vmodtool, new varnish dependencies...)

HTH



Dridi