Project

General

Profile

action #73366

Updated by okurz over 3 years ago

## Motivation Observation 

 We run **auto_review** aka [openqa_review](https://github.com/os-autoinst/openqa_review) in *GitLab CI*. The output of the script can be seen in the log of the pipeline, which can be hard to read because one has to find the relevant snippets first within the verbose output that we currently use. first. 

 ## Acceptance Criteria 

 TBD - Found jobs are shown as pipeline failures in GitLab CI w/o going into the verbose logs 
 - JUnit output is optional and the script output remains available for e.g. local usage 

 ## Suggestions 

 * - Look into pipelines on https://gitlab.suse.de/openqa/openqa-review/ as part of the *Monitor* step in our [DevOps workflow](https://progress.opensuse.org/projects/qa/wiki/Wiki#Common-tasks-for-team-members) 
 * - *GitLab CI* has support for [JUnit artifacts](https://docs.gitlab.com/ee/ci/pipelines/job_artifacts.html#artifactsreportsjunit) i.e. XML files that contain sections for passed or failed tests. Those could be (ab)used to list the found jobs. The script just needs to add the XML boilerplate and write to a file (this is the same concept we use with CircleCI to render TAP output). 
 * Found jobs could be shown as pipeline failures in GitLab CI w/o going into the verbose logs 
 * JUnit output is optional and the script output remains available for e.g. local usage 

Back