-
This requires the COVERITY_SCAN_TOKEN as listed on the project settings page in coverity itself. The intention here is to run this as a scheduled job, with the pipeline schedule itself controlling the branch name etc. This way we can keep the gitlab CI simple enough and just check for COVERITY_SCAN_TOKEN itself. This job shouldn't ever fail unless coverity is down (we'll fix that then), the results of the coverity run are sent to the user that owns the the scheduled pipeline, i.e. me. Because coverity does not currently work on F32 (invalid GNU version number: 101), we force this to run on F31. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
04e61248
Validating GitLab CI configuration…
Learn more