action #160092
opencoordination #99303: [saga][epic] Future improvements for SUSE Maintenance QA workflows with fully automated testing, approval and release
coordination #109644: [epic] Future improvements for qem-bot
Consider using https://docs.gitlab.com/ee/ci/jobs/job_artifacts.html to have static links to always most recent job runs
0%
Description
Motivation¶
Often people ask about qem-bot and what the latest status is, how a certain incident or release request is handled, if tests are triggered, why certain release requests are not yet approved, etc. Then we point people to https://gitlab.suse.de/qa-maintenance/bot-ng/-/jobs or https://gitlab.suse.de/qa-maintenance/bot-ng/-/pipeline_schedules to find the latest jobs for a certain pipeline which is inconvenient, complicated and tedious. Possibly with the use of https://docs.gitlab.com/ee/ci/jobs/job_artifacts.html we could provide direct, always valid links to the log files of the always latest run or even combine artifacts. We might be able to put those links directly into the dashboard web page then.
Acceptance criteria¶
- AC1: An easy to reach web interface references the always latest logs from qem-bot runs
Suggestions¶
- Look into https://docs.gitlab.com/ee/ci/jobs/job_artifacts.html and see if that can be applied to provide always latest logs with static links
- Put those links on an convenient page, e.g. as static links on http://dashboard.qam.suse.de/ or https://gitlab.suse.de/qa-maintenance/bot-ng/ README and point to that README from the dashboard or elsewhere
No data to display