Automation for new spec failure issue creation
Objective
To automate creating of issue to capture a new broken spec in master pipeline.
Context
Triage of #broken-master
channel involves creating a new issue for each new spec failure discovered. This usually involves the following:
- Open the job URL from slack
- Look for failed test in rspec logs
- Open a new issue form in
gitlab-org/gitlab
- Copy & paste failed spec file and line number into issue title
- Copy & paste job failure trace into issue description
- Submit (create) issue
- Copy new issue URL to slack
Proposal
- Create job artifact to capture failed spec file and the line number. This could be a json of "path_to/abc_spec.rb:123" => "snippets of job failure"
- Create post-test job that does the following when there is a failure:
- check if an issue already exists
- if none exists, create issue using the above artifact.
- Post the issue URL to slack
#master-broken
/cc @gl-quality/eng-prod WDYT? Can we leverage anything in the flaky examples report?
Edited by Albert Salim