Remove main-pipeline-report.yml (!9317) · Merge requests · Sylva-projects / sylva-core

What does this MR do and why?

Remove main-pipeline-report.yml and the uncovered commits script folder.

This is a follow up as we move:

scheduled pipeline report (https://gitlab.com/sylva-projects/sylva-elements/ci-tooling/ci-components/scheduled-pipeline-report)
uncovered commits report (https://gitlab.com/sylva-projects/sylva-elements/ci-tooling/ci-components

into dedicated components, and we use them in a dedicated repo.

This avoid to maintain this code in Sylva-core

Need:sylva-projects/sylva-elements/ci-reports!1 (merged)

New schedules configured and ready here: https://gitlab.com/sylva-projects/sylva-elements/ci-reports/-/pipeline_schedules

Uncovered report:

https://sylva-projects.gitlab.io/sylva-elements/ci-reports/uncovered-commits-report/

Schedule pipelines reports:

When the cleanup will be merged, I will stop the sylva-core environment and udpate the wiki links

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 29, 2026 by Loic Nicolle

Remove main-pipeline-report.yml

What does this MR do and why?

Related reference(s)

Test coverage

CI configuration

Global config for deployment pipelines

Merge request reports