This will help to ensure we move towards a single branching strategy
- Use dev cluster to spin up ephemeral tests in the test namespace
- MR pipeline should have a manual intervention stage if a review is required - like product review
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| In Progress | RThomas-WMF | T358575 Kubernetes(k8s) platform for Enterprise Applications | |||
| Open | None | T384574 [APP: Objective 3 Term 3.3. - WME OKR TBD- Q1-Q2 FY 25-26]- Gitlab on k8s | |||
| Open | This.chris.corriere | T410900 Enable ephemeral tests setup for MR pipeline |
Event Timeline
Comment Actions
I was asked to hold off on this ticket until further details on an ephemeral testing strategy have been provided.
initial ephemeral testing options discussed included:
- integration tests
- dynamic security analysis
- performance testing
Comment Actions
tentative plan to discuss:
Trunk-based development with ephemeral envs for MRs and ci-* branches
Final State:
- main to pr (production only)
- MRs to ephemeral environments
- dv removed after migration (replaced by ephemeral)
- Naming: mr-123, ci-feature-x patterns for namespaces, URLs
- Infrastructure: Single service, namespace isolation, shared dev infrastructure with prefixes
- Lifecycle: Auto-create/destroy with grace periods
Comment Actions
After syncing with Jose we're focusing on e2e-framework since it leverages KinD and should be compatible with the new runners.