-
Feature
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
False
-
-
False
-
Not Selected
-
100% To Do, 0% In Progress, 0% Done
-
0
Goal
As a QE of OCM team, we have the responsibility to keep CI jobs stable and continuous running reliable.
Benefit Hypothesis:
Reliable and enough coverage CI jobs can reduce manual work from the whole QE team. And can support CI/CD continuously for version release or deployment. Components should include
- OCM backend CI jobs
- ROSACLI CI jobs
- RHCS CI jobs
- OCMCLI jobs(TBD)
Resources
Automation goal of OCM QE team
CI jobs owned by OCM QE and CI watchers
CI matrix for the testing profiles configuration
Responsibilities
| CI Watcher | 1. Watch CI result and coordinate failure debug efforts to ensure all failures are debugged |
| 2. Collect debug result from team members and fill in CI result in this sheet | |
| Feature Owner | 1. If the failure is your automation issue, run the failed cases by manual to ensure functions work well if time not permit for code fix |
| 2. Open a Jira Ticket in OCM project for your automation fix and Fix it in two weeks | |
| 3. Update your debug result to CI watcher: Pass by manual or Failed with product bugs |
Success Criteria
features and epics are under tracking and updating all the time. The CI jobs and cases are handled by each team member in time.
Results
The tracked features will be reviewed each quarter
- relates to
-
-
- New
-
-
-
- In Progress
-
-
-
- In Progress
-
-
-
- In Progress
-
