fix how shell script framework infers sylva-core Git branch from Git tag (!7044) · Merge requests · Sylva-projects / sylva-core

Closes #3661 (closed)

The code introduced in !6402 (merged) was using a wrong sed regex syntax, relying on \d to match numbers which does not exist in sed, defeating the purpose of the filtering done to always prefer main or release-x.y branches rather than any other dev branch.

The problem can be reproduced with:

$ SYLVA_CORE_COMMIT=fd17b91913e0e6e7f10ea8da7b69f7d5123e3e9c     # commit for 1.6.8
$ git branch --remotes --contains $SYLVA_CORE_COMMIT --format='%(refname:short)' | sed -E 's:^origin(/|$)::' | (grep -v '^$' || true) | sed -E 's/^(main|release-\d+[.]\d+)$/0 &/; t; s/^/1 /' | sort -k1,1 | head -n 1 | cut -d' ' -f2-
cherry-pick-0376b71e

...which isn't the branch name that we want to have.

And with the corrected regex, we get:

$ git branch --remotes --contains $SYLVA_CORE_COMMIT --format='%(refname:short)' | sed -E 's:^origin(/|$)::' | (grep -v '^$' || true) | sed -E 's/^(main|release-[0-9]+[.][0-9]+)$/0 &/; t; s/^/1 /' | sort -k1,1 | head -n 1 | cut -d' ' -f2-
release-1.6

... which is what we need.

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	`light-deploy`, `dev-sources`, `ha`, `misc`, `maxsurge-0`, `logging`, `no-logging`, `cilium`
🎬	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.

Edited Feb 25, 2026 by Thomas Morin

fix how shell script framework infers sylva-core Git branch from Git tag

CI configuration

Global config for deployment pipelines

Merge request reports