#### Why The most repetitive work of QA work is something in on-call ```mermaid graph TD A[check pipeline status] B[retry failed jobs] C[create record issue with qa failure template] D[finish on-call] A --> |all jobs are passed| D A --> |some jobs are failed| B B --> |retry several times| C C --> |find root cause| D ``` #### What Could triage-ops can automated this process-from ```check pipeline status``` to ```create record issue```. #### Tips 1. E2E tests pipelines are running in different [instance](https://dev-ops.gitlab.cn/) and the record issues are created on [quality](https://jihulab.com/gitlab-cn/quality/pipeline-triage/-/issues) in our SaaS, which means we need to support 2 different access token. 2. we can [retry-a-job](https://docs.gitlab.com/ee/api/jobs.html#retry-a-job) and [retry-jobs-in-pipeline](https://docs.gitlab.com/ee/api/pipelines.html#retry-jobs-in-a-pipeline).