Add "knapsack-report-issues" command
What does this MR do and why?
Re: gitlab-org/quality/engineering-productivity/team#354 (closed)
Screenshots or screen recordings
These are strongly recommended to assist reviewers and reduce the time to merge your change.
How to set up and validate locally
- Run the following command (Use a valid
GITLAB_API_TOKEN
):
CI_PIPELINE_IID="1130016183" \
CI_PIPELINE_URL="https://gitlab.com/gitlab-org/gitlab/-/pipelines/1130016183" \
CI_PIPELINE_CREATED_AT="2022-01-31T16:47:55Z" \
CI_JOB_URL="https://gitlab.com/gitlab-org/gitlab/-/jobs/5879543124" \
CI_JOB_NAME_SLUG="rspec unit pg15 9/32" \
exe/knapsack-report-issues -i spec/gitlab_quality/test_tooling/report/fixtures/knapsack-reports/rspec*_slow_report.json -e "spec/gitlab_quality/test_tooling/report/fixtures/knapsack-reports/node_specs_expected_duration.json" -t $GITLAB_API_TOKEN -p "52835425"
This will create an issue in https://gitlab.com/gitlab-org/quality/engineering-productivity/job-timeout-incidents-playground such as gitlab-org/quality/engineering-productivity/job-timeout-incidents-playground#8.
- Close the issue that was created, and rerun the above command - this step should re-open the closed issue and update the issue description with another table
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Edited by Jennifer Li