action #114415

coordination #99303: [saga][epic] Future improvements for SUSE Maintenance QA workflows with fully automated testing, approval and release

coordination #97121: [epic] enable qem-bot comments on IBS (was: enable qa-maintenance/openQABot comments on smelt again)

[timeboxed:10h][spike solution] qem-bot comments on IBS size:S

Added by okurz 2 months ago. Updated 2 months ago.

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


Estimated time:


Acceptance criteria

  • AC1: As soon as testing for an individual release request is finished and if there is at least one failing openQA test a comment is written in IBS informing about the failing openQA tests
  • AC2: If there is no failing openQA test related to an individual release request no comment is written
  • AC3: Only a single comment is ever written on a release request (an existing comment can be updated)


  • Take a look how the openSUSE maintenance bot works in

  • Within qem-bot we already have the feature to send out comments but it seems so far it does not look at the state of openQA jobs so it writes a comment for all release requests whenever triggered which means informing even about all currently running jobs. Maybe the next best task is to actually look at the state and only inform about failing openQA tests

  • Think about moving the trigger point of sending a comment into the approval step of qem-bot or something so when no automatic approval is done instead a comment is written. This is where each individual release request should be looked at

  • Find out if OBS API supports editing comments, otherwise maybe delete old comments (

  • Ensure that only a single comment is written, not multiple whenever qem-bot is called, so either update the existing or delete the old one if OBS does not support updating existing comments


#1 Updated by cdywan 2 months ago

  • Subject changed from [timeboxed:10h][spike solution] qem-bot comments on IBS to [timeboxed:10h][spike solution] qem-bot comments on IBS size:S
  • Description updated (diff)
  • Status changed from New to Workable

#2 Updated by osukup 2 months ago

it will cause same thing as before ... big bunch of emails to anybody related to Incident/ReleaseRequest.

btw. comment code in bot was +- taken from opensuse maintenance bot.

#3 Updated by okurz 2 months ago

osukup wrote:

it will cause same thing as before ... big bunch of emails to anybody related to Incident/ReleaseRequest.

Sure, anyone can opt to disable notifications and tweak in OBS now. But it should be significantly less emails when we only send emails if openQA jobs actually finished and failed (not just based on time schedule informing also about running jobs), right?

Also available in: Atom PDF