Project

General

Profile

action #104841

coordination #80142: [saga][epic] Scale out: Redundant/load-balancing deployments of openQA, easy containers, containers on kubernetes

coordination #80908: [epic] Continuous deployment (package upgrade or config update) without interrupting currently running openQA jobs

Prevent empty changelog messages from osd-deployment when there are no changes size:M

Added by okurz 4 months ago. Updated 4 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
mkittler
Category:
Feature requests
Target version:
Ready
Start date:
2022-01-12
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Motivation

With now daily deployment of OSD we have cases of deployments that have no actual changes in openQA and not in os-autoinst which causes emails with empty changelog, like http://mailman.suse.de/mlarch/SuSE/openqa/2022/openqa.2022.01/msg00012.html with body:

Hi all,
You can find the details on https://gitlab.suse.de/openqa/osd-deployment/-/jobs/776707
As always, if you encounter problems, please file tickets on https://progress.opensuse.org.
Have fun, your QA tools team






os-autoinst changes:

Acceptance criteria

  • AC1: No empty changelog message is sent by email if there are no changes

Suggestions

  • Skip sending the sending the email.

Out of scope

  • Checking if packages were upgraded, or other changes unrelated to the changelog

History

#1 Updated by cdywan 4 months ago

  • Subject changed from Prevent empty changelog messages from osd-deployment when there are no changes to Prevent empty changelog messages from osd-deployment when there are no changes size:M
  • Description updated (diff)
  • Status changed from New to Workable

#2 Updated by mkittler 4 months ago

  • Assignee set to mkittler

#3 Updated by mkittler 4 months ago

  • Status changed from Workable to In Progress

#5 Updated by openqa_review 4 months ago

  • Due date set to 2022-01-29

Setting due date based on mean cycle time of SUSE QE Tools

#6 Updated by mkittler 4 months ago

  • Status changed from In Progress to Feedback

Merged the SR, let's see whether it works.

#7 Updated by mkittler 4 months ago

I'm only waiting for one case of an empty update happening in production but so far we were busy enough to always have at least one change per day.

#8 Updated by mkittler 4 months ago

  • Due date deleted (2022-01-29)

I re-triggered the deployment (after there were no changes) and no empty mail was sent.

#9 Updated by mkittler 4 months ago

  • Status changed from Feedback to Resolved

Also available in: Atom PDF