Coverity no longer accepts reports from CentOS7 containers because the coverity version is too old

[tmadlener]

This is potentially related to #5. Should simply switching a coverity workflow to use an el9 based LCG release work?

[andresailer]

I already changed that 16f38a9 ? (I don't even remember...)

[andresailer]

Yes, switching the workflows to use the el9 instead of latest tag for the container should be it.

[tmadlener]

Not quite yet it seems: https://github.com/AIDASoft/podio/actions/runs/7246402281/job/19738267861#step:4:124

I am not entirely sure why though, because readline-devel should be in the installed packages for the e9 image:

management/el9/packages.txt

Line 39 in 16f38a9

readline-devel

[andresailer]

It still used the latest container instead of el9

[tmadlener]

So, do we push the el9 based coverity container to latest, or should I explicitly ask for coverity:el9 as container in the workflow (that I have to touch in any case to update the LCG release to an el9 based one)?

[andresailer]

Now that the centos7 coverity build silently fails, we might as well push el9 to latest.

[andresailer]

latest now points to el9

[tmadlener]

And at least podio has working coverity scans again :)