-
Epic
-
Resolution: Unresolved
-
Minor
-
None
-
Standardize and Streamline CI/CD Workflows Across CKI Projects
-
False
-
-
False
-
To Do
-
rhel-arr-cki
The CI/CD workflows across CKI repositories have grown organically and inconsistently, leading to fragmented configurations, duplicated logic, and varying developer experiences. Developers often encounter discrepancies between local and CI environments, slow or noisy pipelines, and inconsistent feedback when running linters, tests, or other quality checks.
This epic aims to *standardize and streamline CI/CD practices across all CKI projects, with the goals of improving **pipeline performance, **developer feedback loops, and **maintainability* of CI infrastructure.
Key objectives include:
- *Unify linting and testing configurations*, using centralized tools like Ruff and shared test setups to reduce inconsistencies and eliminate redundant linters or tooling.
- *Improve local–CI parity*, ensuring developers receive the same feedback locally as they do in CI. https://gitlab.com/cki-project/cki-lib/-/merge_requests/853
- *Optimize feedback loops*, by prioritizing fast, clear, and incremental CI feedback (e.g., warn-only stages, staged enforcement of rules).
- *Phase out legacy tooling* and redundant configurations, consolidating around shared standards and reusable components in `cki-lib`.
- *Ensure extensibility*, so teams can adopt project-specific needs while remaining compliant with the standardized core.
By aligning all CKI repositories under a consistent CI/CD strategy, we aim to simplify onboarding, reduce maintenance overhead, and make development faster and more reliable.
Jira: CKI-7164