-
Epic
-
Resolution: Unresolved
-
Major
-
ACM 2.17.0
-
[Tech Debt] Refactor Server Foundation Repo's CI Check Status.
-
Future Sustainability
-
False
-
-
False
-
Not Selected
-
To Do
-
SF Train-37
OCP/Telco Definition of Done
https://docs.google.com/document/d/1TP2Av7zHXz4_fmeX4q9HB0m9cqSZ4F6Jd4AiVoaF_2s/edit#heading=h.gaa58bzbvwde
Epic Template descriptions and documentation.
https://docs.google.com/document/d/14CUCEg6hQ_jpsFzJtWo29GfFVWmun2Uivrxq3_Fkgdg/edit
ACM-wide Product Requirements (Top-level Epics)
https://docs.google.com/document/d/1uIp6nS2QZ766UFuZBaC9USs8dW_I5wVdtYF9sUObYKg/edit
*<--- Cut-n-Paste the entire contents of this description into your new
Epic --->*
Epic Goal
Currently, 53% of the server foundation's repositories or branches have issues with CI checks. Some are simple SonarCloud configuration errors, while others are more complex problems, such as E2E flaky errors.
Why is this important?
As we adopt a more proactive and strict CVE fix policy, these CI issues across different branches often become blockers at critical release stages, affecting our release speed and confidence.
In this Epic, we plan to systematically resolve the CI check issues for every active branch in each repository, based on the table above. Our goal is to ensure that every fix is merged quickly and safely.
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)