action #102206

QA - coordination #91646: [saga][epic] SUSE Maintenance QA workflows with fully automated testing, approval and release

QA - action #97274: qam dashboard improvement ideas

Make bot-ng a proper public open source project size:M

Added by okurz 3 months ago. Updated about 21 hours ago.

Feature requests
Target version:
Start date:
Due date:
% Done:


Estimated time:



Followup to #94838

Acceptance criteria


  • Look at the ansible deployment pipeline (in qa-maintenance)

Out of scope

  • New tests or features (see epic)

Related issues

Copied from openQA Project - action #94838: Make qem-dashboard a proper public open source project size:MResolved2021-06-292021-12-18


#1 Updated by okurz 3 months ago

  • Copied from action #94838: Make qem-dashboard a proper public open source project size:M added

#2 Updated by okurz 3 months ago

Added to backlog as discussed during midweekly unblock meeting within SUSE QE Tools 2021-11-10 as we covered this topic. kraih wanted to volunteer for #94838 and this is closely related.

#3 Updated by cdywan 3 months ago

  • Subject changed from Make qem-dashboard surrounding tooling proper public open source projects as well to Make bot-ng a proper public open source project size:M
  • Description updated (diff)
  • Status changed from New to Workable
  • Parent task set to #97274

#4 Updated by okurz about 1 month ago

#94838 was successfully completed. With that approach we managed to still run gitlab CI pipelines. We can either follow the same approach for bot-ng or similar as we do for along with

#5 Updated by okurz 3 days ago

  • Status changed from Workable to In Progress
  • Assignee set to okurz

I am ready to take this myself then. IMHO for creating a project on github we should think about a good name. "bot-ng" itself is ambiguous so a project like wouldn't be a good idea. This is why I always consider the full name to be "qa-maintenance/bot-ng". How about "qambot"? A one-line explanation describing the project could then be "The SUSE QA Maintenance bot for openQA". For a complete project name I suggest "" and as alternative "". Any opinions?

Regarding deployment we are currently using gitlab CI with periodic schedule based executions within the gitlab CI pipelines based on container images. So in my understanding we can simply exchange the container image to use one from including SUSE CA certificates, e.g. just like and use the latest container images in each execution cycle so there is no impact where the code is maintained.

#6 Updated by okurz 2 days ago

Asked in weekly unblock of the team. We decided that we favor as a name.

#7 Updated by okurz 1 day ago

Created empty repo and will use the same approach as in #90164 first to mirror the data, then we can softly switch over CI pipelines and test it out before we remove the source from the internal repo. So I created the new github repo, invited the openSUSE/tools-team and "openqa-git-sync". I logged into that account in my browser in a private window using credentials from, copied the invitation URL received by email into that browser instance and accepted the invitation. In I added the URL with the according password. I triggered an update run and has it all. Currently the CI pipeline in uses which comes from . The only internal package in there seems to be . But it seems we only bring in the metadata this way and dependencies. The source code of qem-bot itself so far we cloned in the pipeline from the git repo itself. I propose to change that with to use the github repo directly.

#8 Updated by okurz about 21 hours ago

  • Status changed from In Progress to Feedback

waiting for merge of MR before disabling mirorring again and moving and removing internal source and just keeping the gitlab CI config.

Also available in: Atom PDF