Align API Discovery CI templates with other AST features
What does this MR do and why?
Align API Discovery CI templates with other AST features
Update the stable template to:
- introduce AST_ENABLE_MR_PIPELINES to enable MR pipeline
- default to branch pipeline
- ensure API_DISCOVERY_DISABLED value is either 'true' or '1'
- ensure API_DISCOVERY_DISABLED_FOR_DEFAULT_BRANCH value is either 'true' or '1'
Introduce a latest template that has the same content as stable but has MR pipelines enabled by default.
Warning
This is a breaking change that must ship during window 1
As established in the issue, API discovery already uses MR pipelines by default and this MR aligns it to rather use branch pipelines by default on the stable template.
Note that this MR is currently based on top of the MR containing all the other templates changes because it also provides the tests refactor that I wanted to reuse here. The goal is to merge the main MR and that one during the first window of 18.0 breaking changes.
References
Screenshots or screen recordings
| Before | After |
|---|---|
How to set up and validate locally
MR acceptance checklist
Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Related to #410880 (closed)