Determine which report types can be immediately displayed even before pipeline completion
As mentioned in #369944 (comment 1091682020), here we will discuss and determine which report types are safe to be rendered immediately even before pipeline completes and which are not.
No implementation required at this point yet. The information that will be gathered here will be helpful for us on how to properly design/refactor the implementation for reports if ever.
Will need help updating the table below. The list of report types here are based on https://docs.gitlab.com/ee/ci/yaml/artifacts_reports.html.
report type | can show immediately | extra notes |
---|---|---|
accessibility | ||
api_fuzzing | 1 | |
browser_performance. | ||
cluster_image_scanning | 1 | |
coverage_report | 2 | |
codequality | ||
container_scanning | 1 | |
coverage_fuzzing | 1 | |
cyclonedx | ||
dast | 1 | |
dependency_scanning | 1 | |
dotenv | ||
junit | This is rendered on 2 places, MR Widget and Pipeline tests tab. On the MR widget, this is rendered as comparison. So we may need some indicator that the current report may be incomplete. As new builds finish, the report's reactive cache is invalidated thus will cause re-rendering with updated comparison | |
license_scanning | ||
load_performance | ||
metrics | ||
requirements | ||
sast | 1 | |
secret_detection | 1 | |
terraform |
-
Theses are rendered in 2 places, MR Widget and Pipeline tab. All Security reports are merged and deduped in aggregate upon pipeline completion
↩ ↩ 2↩ 3↩ 4↩ 5↩ 6↩ 7↩ 8 -
Coverage report is only created when the pipeline and its descendants have completed. It does not use
pipeline.complete_and_has_reports?
method.↩