action #156175
closedcoordination #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
Support development of https://github.com/openSUSE/qem-bot/pull/154 size:M
0%
Description
Motivation¶
QE Core and others would like to see improvements to qem-bot. So that we can enable them to develop new features themselves we should support. In this case https://github.com/openSUSE/qem-bot/pull/154 shows a new concept. While the PR is not mergeable yet we can still try out the functionality. For this https://gitlab.suse.de/qa-maintenance/bot-ng/-/merge_requests/65 already exists which we should merge, monitor and most likely revert after we have enough feedback which we should write back in https://github.com/openSUSE/qem-bot/pull/154.
For more context see https://suse.slack.com/archives/C02CANHLANP/p1709051006649099
Acceptance criteria¶
- AC1: It is known if https://github.com/openSUSE/qem-bot/pull/154 can generally work
- AC2: CI jobs in https://gitlab.suse.de/qa-maintenance/bot-ng/ are green (again)
Suggestions¶
- Merge https://gitlab.suse.de/qa-maintenance/bot-ng/-/merge_requests/65 when you are able to also monitor the impact
- Monitor and revert as necessary
- Feed feedback back to https://github.com/openSUSE/qem-bot/pull/154
- Rinse and repeat
Out of scope¶
- Have https://github.com/openSUSE/qem-bot/pull/154 merged
Updated by mkittler 9 months ago
I did another review (https://github.com/openSUSE/qem-bot/pull/154#pullrequestreview-1914213851) and started another discussion on slack.
Updated by mkittler 9 months ago
So this isn't lost in the Slack thread:
- Dependencies for running the bot locally can be looked up here: https://build.suse.de/package/view_file/QA:Maintenance/openSUSE-Leap-Container/Dockerfile?expand=1
- Metadata can be downloaded from here: https://build.suse.de/package/show/QA:Maintenance/qam-metadata
- Then one can run the bot for local testing via e.g.:
./bot-ng.py -c "$PWD/etc" --dry --token foo inc-approve
Updated by openqa_review 9 months ago
- Due date set to 2024-03-22
Setting due date based on mean cycle time of SUSE QE Tools
Updated by szarate 8 months ago
Marius thanks for the hints, I got part of the tests running and it works, now I need to extend the unit tests for cases where an incident has already been released, etc. I think the prio can be lowered, and in the meantime I'll also update the makefile to add a functional test of this.