Use schedule pipeline report component (!9190) · Merge requests · Sylva-projects / sylva-core

What does this MR do and why?

This MR is a first part of moving satellite parts of the Sylva-core CI into dedicated components.

This will allow to have a better re usability of them and a lifecylce independant of Sylva-core CI itself

Implication of this MR:

The code to generate the report will now live in his own dedicated repo ( a dry-run is done in this repo on each MR, another one is done in Sylva core when we change the main-pipeline-report.yml)
Initially we had one scheduled pipeline per release we want to track, with the configuration of the directly set in the variable of the scheduled pipeline. This was really not convenient as it was hidden to nearly everyone. Now we'll have only one schedule pipeline with only one variable (CI_REPORT=true) that will trigger all the jobs for all the release branches. The configuration live here in the component include

Component: sylva-projects/sylva-elements/ci-tooling/ci-components/scheduled-pipeline-report!2 (merged) close #4655 (closed)

Test coverage

CI configuration

Below you can choose test deployment variants to run in this MR's CI.

Click to open to CI configuration

Legend:

Icon	Meaning	Available values
☁️	Infra Provider	`capd`, `capo`, `capm3`
🚀	Bootstrap Provider	`kubeadm` (alias `kadm`), `rke2`, `okd`, `ck8s`
🐧	Node OS	`ubuntu`, `suse`, `na`, `leapmicro`
🛠️	Deployment Options	Deployment option list and description
🎬	Pipeline Scenarios	Available scenario list and description
🟢	Enabled units	Any available units name, by default apply to management and workload cluster. Can be prefixed by `mgmt:` or `wkld:` to be applied only to a specific cluster type
🔴	Disabled units	Any available units name, by default apply to management and workload cluster. Can be prefixed by `mgmt:` or `wkld:` to be applied only to a specific cluster type
🏗️	Target platform	Can be used to select specific deployment environment Available platform list and description
⚡	Pipeline control	`autorun`, `manual` or `blocking`. Can be used to override global config and start a deployment pipeline the required way

Global config for deployment pipelines

autorun pipelines
allow failure on pipelines
record sylvactl events

Notes:

Enabling autorun will make deployment pipelines to be run automatically without human interaction
Disabling allow failure will make deployment pipelines mandatory for pipeline success.
if both autorun and allow failure are disabled, deployment pipelines will need manual triggering but will be blocking the pipeline

Be aware: after configuration change, pipeline is not triggered automatically. Please run it manually (by clicking the run pipeline button in Pipelines tab) or push new code.

Edited Sep 17, 2026 by Loic Nicolle

Use schedule pipeline report component

What does this MR do and why?

Related reference(s)

Test coverage

CI configuration

Global config for deployment pipelines

Merge request reports