action #96998
closed
Increase bus factor for bot-ng size:M
Added by jbaier_cz over 2 years ago.
Updated over 2 years ago.
Description
Motivation¶
Identical story to qa-maintenance/openQABot
Acceptance Criteria¶
- AC1: Users can see the logs of qa-maintenance/bot-ng without special accounts
Suggestions¶
- Copy CI setup from openQABot to qa-maintenance/bot-ng and adapt for "full" and "incident" tests as well as "sync" and "approve" steps
- Ask osukup and jbaier_cz what steps are necessary
Further details¶
https://gitlab.suse.de/qa-maintenance/bot-ng exists
- Copied from action #95221: Provide more people with administrative access to services on qam2.suse.de, at least qa-maintenance/openQABot, i.e. increase bus factor size:M added
- Subject changed from bot-ng: Increase bus factor for size:M to Increase bus factor for bot-ng
- Target version changed from Ready to future
before we work on this can we please clarify what is bot-ng? Where does it live?
If I am not mistaken, that is your missing part from https://progress.opensuse.org/issues/95221#note-18, this is scheduling incidents and full tests and it is using qem-dashboard API for getting/posting the incidents (which is the main difference, openqabot interacts directly with openQA). Also https://progress.opensuse.org/issues/97121#note-3 is practically referring here.
This ticket shall cover moving the code from osukup/bot-ng to qa-maintenance/bot-ng and deploy via GitLab CI for the runs to be visible.
- Description updated (diff)
- Target version changed from future to Ready
- Related to coordination #97121: [epic] enable qem-bot comments on IBS (was: enable qa-maintenance/openQABot comments on smelt again) added
- Subject changed from Increase bus factor for bot-ng to Increase bus factor for bot-ng size:M
- Description updated (diff)
- Status changed from New to Workable
- Status changed from Workable to In Progress
- Assignee set to jbaier_cz
- Due date set to 2021-09-09
Setting due date based on mean cycle time of SUSE QE Tools
- Status changed from In Progress to Feedback
- Due date deleted (
2021-09-09)
- Status changed from Feedback to Resolved
The bot is running inside Gitlab CI and the status is publicly visible: 
A reference to this tool was added to toolchain list (which is mentioned in the team wiki).
Also available in: Atom
PDF