Project

General

Profile

Actions

action #176142

open

coordination #102906: [saga][epic] Increased stability of tests with less "known failures", known incompletes handled automatically within openQA

coordination #175515: [epic] incomplete jobs with "Failed to find an available port: Address already in use"

Re-consider staging instances

Added by livdywan 3 months ago. Updated 3 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Feature requests
Target version:
Start date:
2025-01-24
Due date:
% Done:

0%

Estimated time:

Description

Motivation

In #175518 we reminded ourselves that o3 is effectively a staging instance. As such regressions may hit production by design. Maybe we want to re-consider that?

Acceptance Criteria

  • AC1: There is a common understanding within the tools team about use of "staging instances"

Suggestions

  • Are on demand staging instances quite similar to personal instances in * practice? So little benefit going from past experience.
  • For more context also see the original "continuous delivery" ticket #18006 * "continuous testing + delivery of tested openQA on openSUSE"
  • Research current industry best practices about "staging instances" and where we might want to adopt new ideas
  • Discuss with the team the current use of staging instances
Actions #1

Updated by livdywan 3 months ago

  • Parent task changed from #175518 to #175515
Actions #2

Updated by okurz 3 months ago

  • Assignee set to okurz
Actions #3

Updated by okurz 3 months ago

  • Target version set to Ready
Actions #4

Updated by okurz 3 months ago

  • Tags set to lesson learned, staging, o3, osd
  • Subject changed from Re-consider staging instances? to Re-consider staging instances
  • Description updated (diff)
  • Category set to Feature requests
  • Assignee deleted (okurz)
Actions #5

Updated by okurz 3 months ago

  • Target version changed from Ready to future
Actions

Also available in: Atom PDF