-
Epic
-
Resolution: Unresolved
-
Critical
-
None
-
downstream-quarantine-management
-
Quality / Stability / Reliability
-
77
-
False
-
-
False
-
None
-
To Do
Goal
Implement a comprehensive quarantine management system for downstream environments, establishing clear rules and an automated isolation mechanism. It will utilize scheduled job test data to drive quarantine decisions.
User Stories
- Define downstream-specific quarantine rules aligned with upstream principles, adapted to use scheduled job test results.
- Develop an automated mechanism to identify tests meeting quarantine criteria based on scheduled job data.
- Establish procedures for placing tests into quarantine, assigning ownership, and managing their lifecycle in the downstream context.
- Count the quarantined cases, and weekly report sent for quarantined cases to the reminder team.
- Create processes for removing tests from quarantine once stability criteria are met, using scheduled job data for validation.
- Ensure integration with downstream CI/CD pipelines to enforce quarantine status and maintain test suite stability.
Non-Requirements
- List of things not included in this epic, to alleviate any doubt raised during the grooming process.
Notes
- Any additional details or decisions made/needed
1.
|
upstream roadmap issue |
|
New | |
Unassigned |
2.
|
upstream design |
|
New | |
Unassigned |
3.
|
upstream documentation |
|
New | |
Unassigned |
4.
|
upgrade consideration |
|
New | |
Unassigned |
5.
|
test plans in polarion |
|
New | |
Unassigned |
6.
|
automated tests |
|
New | |
Unassigned |
7.
|
downstream documentation merged |
|
New | |
Unassigned |
8.
|
CNV QE DevOps Requirement/Enablement |
|
New | |
Unassigned |