QA (public) » openQA Project (public)

Motivation¶

• The current setup involving jenkins together with openQA, OBS (and GHA) is not very robust and causes some kind of confusion every time something isn't working right. Maybe we can find an approach that is easier to maintain?

Suggestions¶

• Look into the current setup on http://jenkins.qa.suse.de/ using mostly scripts defined in https://github.com/os-autoinst/scripts/blob/master/trigger-openqa_in_openqa (and maybe others in that repo)
• Find a way to leave Jenkins out of the equation
• Maybe we can use Gitea features as OBS moves to git hosting?
  • https://docs.gitea.com/usage/actions/quickstart
  • YAML could be maintained in git, no need for another tool
• Consider Apache Airflow
• Rely on the openQA web UI
  • Verify state of packages from within openQA
  • OBS integration as a plugin?