[FFmpeg-devel] coverity testing of FFmpeg

Josh de Kock josh at itanimul.li
Sun Nov 27 23:05:47 EET 2016


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 2016/11/27 19:00, Philip Langdale wrote:
> 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

I can help with Travis CI + GitHub, if any is needed, I have used it
extensively with other open-source projects.

- -- 
Josh

PGP fingerprint: A93A602D7A6D3C5388D792BCD052D40DDEF9703D
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJYO0qrAAoJENBS1A3e+XA947MP/RZplh1BTM/Cn0suaCZygIFo
elJyY1uxMGUvABnC4QHvIxpuuq+SewEA9VzbqMrSWV3xSueFZo8wQQTifCnlc69O
oipwzqyaHjqXRSMiAxMpVPAzdEIvslB8aXwdWELKy9GcHkUVn2hEzitBOfi/qL7y
L3m80h5ZgH4UExSyZmqWniJcOgeC/MZWIvLhGmtdsAihGAVQkS2czQKAJtxSMiJT
hEppu6xHWNLEwN3QnTIhuQGvbVlEQUm9A6/C8x74JJe0lWG3YGpWc2I9OJt07I6Z
J6Rstzuk0EPoS/8CaFTjyMrEgc8v+QIpIjY9GCt0pgDsaUEtA8Cq03IL4wHruowi
nJ8ZSJq0uJQtIws0G/uc29bjKqjz3rHTRXS73uYPDFmfG0hp/pbWDF6UoOate2J7
vtwRfl6oDdZOJAXhg+Wr2DMFiwdSK7niboArYxf+z1mooco6RnCI2uthIGCtt3Gb
i4x89YK1jaSKsbBqTmhw3rCCmSIR318p4vdIiwcULJqm5ZaZc3KU/OYYNiOKxkxx
EwzstoGC7yjXwc1S7Ohmu5yPoFWISmFhL15d8zCvDjpAlUCN1Euc5WFdftT2OaEX
pE6nikt/q6KmPQhQsAGCBX/Nd3QeOwBzGKA9qx9cXLtEt8vssgdL93lFTBZM0m+J
dtbGnlFRnzMsCosrFUCL
=jyZO
-----END PGP SIGNATURE-----


More information about the ffmpeg-devel mailing list