[FFmpeg-devel] coverity testing of FFmpeg
Philip Langdale
philipl at overt.org
Sun Nov 27 21:00:21 EET 2016
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sat, 26 Nov 2016 23:55:17 +0100
Michael Niedermayer <michael at niedermayer.cc> wrote:
> Hi all
>
> The machine on which the coverity stuff is is old, both hw and OS.
> the OS will no longer get security updates in a few months and the hw
> does not always boot and its switched off most of the time.
> and it has no other use anymore than running coverity. Ive tried
> to find someone a while ago to take coverity testing over and i
> thought timothy would maybe do it but he seems to not have had any
> time to look into it ...
> and de facto ive not run it regularly in the recent months.
> So this is kinda a louder announcement that if you care about coverity
> testing, you need to do something ...
>
> thx
>
> PS: work would involve installing every optional dependancy of FFmpeg
> (and keep them updated as needed)
> and regularly either manually or automatically git pull, build with
> the coverity tools and upload Its not a huge amount of work but it is
> work
>
Hi Michael,
I think we could do this using travis-ci.
https://scan.coverity.com/travis_ci
travis can be directly connected to the github mirror and then we set
up a coverity job as covered in this doc.
It wouldn't even need to be configured to build - just run the coverity
scan. I'd be happy to investigate this, but I'd need admin permissions
on github to configure travis integration.
- --phil
-----BEGIN PGP SIGNATURE-----
iEYEARECAAYFAlg7LUUACgkQ+NaxlGp1aC5q3QCgyRVxMRL80RSxDqRfj2zixL8D
rIkAn0s6o1bQr/lapHU+ZU2Y/+vWaYFt
=yig7
-----END PGP SIGNATURE-----
More information about the ffmpeg-devel
mailing list