Actions
action #176142
opencoordination #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
Start date:
2025-01-24
Due date:
% Done:
0%
Estimated time:
Tags:
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