ci: Expose tests metadata via Pages
requested to merge 335675-consider-storing-retrieving-tests-metadata-in-from-pages-instead-of-artifacts into master
What does this MR do?
Currently, we store and retrieve the Knapsack report, Flaky tests report, and Test mappings in/from artifacts: https://gitlab.com/gitlab-org/gitlab/-/blob/1c737e466e7336e6ca1111e8fe96034126e09b13/scripts/rspec_helpers.sh#L3-70
This MR exposes these files using Pages instead for the following reasons:
- We're only interested in the latest state of these files, so using Pages makes sense here
- That would simplify the logic to retrieve these files (currently, we first look for the job ID, and then download its artifacts)
- That would reduce the load on GitLab.com's infrastructure as serving static files from Pages is much cheaper than performing multiple API calls to retrieve the job and artifacts
- That would make https://gitlab.com/gitlab-org/quality/team-tasks/-/issues/943 not needed as requests to Pages don't need to be authenticated (as long as the pages are public)
If the files are successfully exposed via Pages, we should be able to migrate our current usage of artifacts to retrieving these files through:
- https://gitlab-org.gitlab.io/gitlab/knapsack/report-master.json
- https://gitlab-org.gitlab.io/gitlab/rspec_flaky/report-suite.json
- https://gitlab-org.gitlab.io/gitlab/crystalball/packed-mapping.json.gz
Related to #335675 (closed).
Edited by Rémy Coutable