action #52655
closedopenQA Project (public) - coordination #39719: [saga][epic] Detection of "known failures" for stable tests, easy test results review and easy tracking of known issues
[epic] Move openqa-review from cron-jobs on lord.arch to a more sustainable long-term solution
100%
Description
Motivation¶
Currently the reports are generated on lord.arch by the user "okurz". We can look for a more sustainable long-term solution
Suggestions¶
we could run openqa-review
- in gitlab CI
- on GOCD at botmaster.suse.de
- on a QA SLE VM
for "gocd", from #openqa-dev (rc):
I asked coolo "WDYT running "openqa-review" which generates e.g. https://w3.nue.suse.com/~okurz/openqa_sle15_status.html on botmaster.suse.de GOCD? Would you accept a PR adding that to GOCD? In this case, what else would I need to test it out and get it to run?".
He is fine to run it on botmaster.suse.de. I am checking the deps with the container def. https://build.opensuse.org/package/view_file/openSUSE:Tools:Images/gocd-agent-release-tools/Dockerfile?expand=1 is installed. `zypper -n in python3-openqa_review && openqa-review …" would not work. The scripts run as user "go". Either the script is part of the container (and won't change) - or it should run from a git. The containers are running constantly - they are not per job. The container change on deployment of gocd, they only contain dependencies and the gocd agent. If we need new dependencies, I can inject zypper -n calls on every container so run from git checkout - this way you also track which job ran on which revision. Basically all of them run from git checkout, https://github.com/openSUSE/openSUSE-release-tools/blob/master/gocd/autosubmit.gocd.yaml is a good example. I would need additional deps "python3-appdirs python3-beautifulsoup4 python3-future python3-humanfriendly python3-setuptools python3-sortedcontainers python3-soupsieve" to make it run directly from git.
I am not fully convinced to go to botmaster.suse.de with gocd considering that this would mean to not use the RPM package but run from git but build the container with missing dependencies which I am not sure if it's the right approach.