Create a tooling to check if some commit are not covered by a tag in sylva-elements/*** repos (!7320) · Merge requests · Sylva-projects / sylva-core

What does this MR do and why?

New python script used on a scheduled pipeline to analyse sylva-elements repo and detects if some new commits are not covered by tag on protected branches (main, release-x.y).

The script can produces a markdown report but also a json file containing all data related (repos, branches, tags, commits). An HTML report is also included (build by Claude AI generator), the HTML report template is able to load the JSON file to fill dashboard.

The scheduled pipeline will publish report on this page: https://sylva-projects.gitlab.io/sylva-core/_uncovered_commits/

This dashboard allows user to apply some filters:

per project
branches OK
branches with uncovered commits
branches without any tag

For branches with uncovered commits, details displays list of all uncovered commits with links to gitlab..

When working on MR, if any change occurs to files related to uncovered_commits reports a manual job will be available, in order to iterate quickly on merge-request, we limit scanned repositories to a few ones.

closes #1424 (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 (i.e `real-bmh` for capm3 )

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.

Closes #1424 (closed)

Edited Aug 05, 2026 by Alexandre Seitz

Create a tooling to check if some commit are not covered by a tag in sylva-elements/*** repos

What does this MR do and why?

Related reference(s)

Test coverage

CI configuration

Global config for deployment pipelines

Merge request reports