Fix confusing C/C++ example for test coverage reporting
What does this MR do and why?
This merge fixes the C/C++ example for test coverage visualization. It is confusing, that the example
uses both the coverage:
regex filter and the artifact
directive. I would assume, that the artifact
would suffice to create the repo analytics. Additionally, I encountered an unexpected behaviour, where
the regex would not parse the docker build
phase.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.