Project

General

Profile

Actions

action #104841

closed

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 over 2 years ago. Updated about 2 years ago.

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

0%

Estimated time:

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
Actions #1

Updated by livdywan over 2 years 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
Actions #2

Updated by mkittler over 2 years ago

  • Assignee set to mkittler
Actions #3

Updated by mkittler over 2 years ago

  • Status changed from Workable to In Progress
Actions #5

Updated by openqa_review over 2 years ago

  • Due date set to 2022-01-29

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

Actions #6

Updated by mkittler over 2 years ago

  • Status changed from In Progress to Feedback

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

Actions #7

Updated by mkittler about 2 years 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.

Actions #8

Updated by mkittler about 2 years ago

  • Due date deleted (2022-01-29)

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

Actions #9

Updated by mkittler about 2 years ago

  • Status changed from Feedback to Resolved
Actions

Also available in: Atom PDF