-
Epic
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
Incorporate automation from Site-Config / CAPOA / CAPMetal into ACM's Jenkins Pipelines
-
Quality / Stability / Reliability
-
False
-
-
False
-
Green
-
To Do
Epic Goal
Integrate automation for Site-config / CAPOA / CAPMetal with ACM's Jenkins pipelines.
Why is this important?
To be able to trigger site-config / CAPOA / CAPMetal tests automatically every time ACM regression test is run.
Scenarios
...
Acceptance Criteria
...
Dependencies (internal and external)
- ...
Previous Work (Optional):
- ...
Open questions:
- …
Done Checklist
- CI - CI is running, tests are automated and merged.
- Release Enablement <link to Feature Enablement Presentation>
- DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
Issue> - DEV - Upstream documentation merged: <link to meaningful PR or GitHub
Issue> - DEV - Downstream build attached to advisory: <link to errata>
- QE - Test plans in Polarion: <link or reference to Polarion>
- QE - Automated tests merged: <link or reference to automated tests>
- DOC - Doc issue opened with a completed template. Separate doc issue
opened for any deprecation, removal, or any current known
issue/troubleshooting removal from the doc, if applicable. - Considerations were made for Extended Update Support (EUS)
Note:
Currently ipv6 is not in scope.