Fix artifact file path for actual knapsack report
What does this MR do and why?
I discovered that Duration Analysis
stopped working on master broken incidents recently such as gitlab-org/quality/engineering-productivity/master-broken-incidents#5197 (closed). I realized that one of the artifact file path is changed.
Example:
- This is the current path of the actual duration report generated by Knapsack: https://gitlab.com/gitlab-org/gitlab/-/jobs/6106106267/artifacts/external_file/knapsack/rspec-ee_unit_pg14_20_28_278964_report.json
- in the past, this artifact file did not have the
project id
substring, so instead ofrspec-ee_unit_pg14_20_28_278964_report.json
, it wasrspec-ee_unit_pg14_20_28_report.json
. Triage-ops needs to add in theproject id
to the file name to fix this problem.
Expected impact & dry-runs
These are strongly recommended to assist reviewers and reduce the time to merge your change.
See https://gitlab.com/gitlab-org/quality/triage-ops/-/tree/master/doc/scheduled#testing-policies-with-a-dry-run on how to perform dry-runs for new policies.
See https://gitlab.com/gitlab-org/quality/triage-ops/-/blob/master/doc/reactive/best_practices.md#use-the-sandbox-to-test-new-processors on how to make sure a new processor can be tested.
Action items
-
If adding environment variables for reactive processors, update config/triage-web.yaml
and.gitlab/ci/triage-web.yml
-
(If applicable) Add documentation to the handbook pages for Triage Operations => - (If applicable) Identify the affected groups and how to communicate to them:
-
/cc @ person_or_group
=> -
Relevant Slack channels => -
Engineering week-in-review
-