Leverage Pages for coverage and other reports
CI/CD Pipelines often create artifacts that are designed for human consumption such as coverage reports. There are a few issues about surfacing this information better. Currently you can specify a report's output directory as an artifact, which makes it available for download, but if the report is HTML, wouldn't it be nice to just display that information in the browser? GitLab CE's pipeline now generates a coverage report and publishes it using Pages. Perhaps we can generalize this and make it available for others. I imagine some of the challenges will be around Pages being public whereas coverage reports may need to be restricted. Other challenges will be around multiple artifacts. What if you want a coverage report, a code-climate-esque report, and a security vulnerability report? A naive solution might be to just render HTML pages rather than have them for download, but I imagine that has complications that Pages overcomes.
Links / references
- JUnit (XUnit) is an attempt and making a standard format for test results which could then be parsed and displayed as a native element in GitLab. Other vendors have taken this approach. Unfortunately JUnit isn't very popular with modern development stacks, and the results aren't always great either. It's also limited to test results, whereas coverage, security, etc. are also interesting report-style artifacts.