### Description Artifacts created by jobs are sometimes useful to be rendered in a very specific way. They can be for example test output or reports. We already have a way to show HTML artifacts online (gitlab-ce#34102), but it is not the same case: it may not be possible to easily convert output into HTML pages, and sometimes we need to bind results directly to the specific job. ### Proposal Implement specific CI Views for a defined set of artifacts, that will be identified and rendered in a specific way. Artifacts will also be available using the generic artifacts browser, the HTML viewer and can be downloaded. Artifacts can be created and stored as usual, but we need some additional implementation to make it available. - artifacts should be accessed easily in the view (retrieval could be similar to `codeclimate.json` for Code Quality) - `.gitlab-ci.yml` must define a syntax to set the viewer we want to use for the specific job ```yaml artifacts: paths: - name: codeclimate.json type: codequality - name: gl-sast-report.json type: sast ``` The list of CI Views we want to implement is the following: - [x] JUnit/xUnit: https://gitlab.com/gitlab-org/gitlab/issues/24792 (12.5) - [ ] Selenium: https://gitlab.com/gitlab-org/gitlab/issues/6061 - [x] SAST: https://gitlab.com/gitlab-org/gitlab-ee/issues/3776 (10.6) - [ ] Code Quality: https://gitlab.com/gitlab-org/gitlab/issues/4189