-
Epic
-
Resolution: Done
-
Undefined
-
None
-
None
-
Implement proper CI/CD and branching strategy for HAC Dev
-
False
-
False
-
None
-
0% To Do, 0% In Progress, 100% Done
Acceptance Criteria
- Should implement proper CI/CD strategy for HAC Dev where rollouts to prod and dev clusters are separated.
- Should configure CD in such a way that every new build is pushed to dev cluster automatically.
- Should configure CD such that push to prod requires a manual update of latest image tag.
- Should implement a branching strategy for hac-dev repo such that development can continue on main.next branch in case of code freeze.
1.
|
DOD: Training materials supplied to Support/SRE |
|
To Do | 
|
Unassigned |
2.
|
DOD: Docs verified by QE |
|
To Do |
|
Unassigned |
3.
|
DOD: Docs completed and merged |
|
To Do |
|
Unassigned |
4.
|
DOD: All known issues captured and blockers resolved |
|
To Do |
|
Unassigned |
5.
|
DOD: Code merged for regular build/release testing in the HAC Common CI/CD framework |
|
To Do |
|
Unassigned |
6.
|
DOD: CI runs successfully with test automation |
|
To Do |
|
Unassigned |
7.
|
DOD: Automated/Integrated tests complete |
|
To Do |
|
Unassigned |
8.
|
DOD: Architectural artifacts completed, reviewed and stored |
|
To Do |
|
Unassigned |
9.
|
DOD: Product Manager and UX signed off on solution |
|
To Do |
|
Unassigned |
10.
|
DOD: Acceptance criteria related to this Epic has been identified and met |
|
To Do |
|
Unassigned |