Track sylva_diskimagebuilder_version and sylva_kiwi_imagebuilder_version from previous release with renovate (!6098) · Merge requests · Sylva-projects / sylva-core

What does this MR do and why?

Follow up of discussion from: !6005 (merged)

Add a renovate configuration to track the sylva_diskimagebuilder_version version defined in previous release branch.

This renovate configuration is based on a custom datasource, we have to specify the URL to check (as the template doesn't seem to support custom field, we have to pass the whole URL).

When we'll create a new release branch the registryUrl field in the renovate comment will require an update to target the correct branches

Related reference(s)

Test coverage

Dry-run extract:

           {
             "deps": [
               {
                 "depName": "diskimagebuilder-n-1",
                 "currentValue": "0.5.13",
                 "datasource": "custom.checking-diskimagebuilder-version",
                 "versioning": "loose",
                 "registryUrls": [
                   "https://gitlab.com/sylva-projects/sylva-core/-/raw/release-1.5/charts/sylva-units/values.yaml"
                 ],
                 "replaceString": "\n    # renovate: custom datasource registryUrl=https://gitlab.com/sylva-projects/sylva-core/-/raw/release-1.5/charts/sylva-units/values.yaml depName=diskimagebuilder-n-1 datasource=custom.checking-diskimagebuilder-version\n    tag: 0.5.13",
                 "updates": [],
                 "packageName": "diskimagebuilder-n-1",
                 "warnings": [],
                 "registryUrl": "https://gitlab.com/sylva-projects/sylva-core/-/raw/release-1.5/charts/sylva-units/values.yaml",
                 "currentVersion": "0.5.13",
                 "fixedVersion": "0.5.13"
               },
               {
                 "depName": "diskimagebuilder-n-2",
                 "currentValue": "0.4.18",
                 "datasource": "custom.checking-diskimagebuilder-version",
                 "versioning": "loose",
                 "registryUrls": [
                   "https://gitlab.com/sylva-projects/sylva-core/-/raw/release-1.4/charts/sylva-units/values.yaml"
                 ],
                 "replaceString": "\n    # renovate: custom datasource registryUrl=https://gitlab.com/sylva-projects/sylva-core/-/raw/release-1.4/charts/sylva-units/values.yaml depName=diskimagebuilder-n-2 datasource=custom.checking-diskimagebuilder-version\n    tag: 0.4.18",
                 "updates": [],
                 "packageName": "diskimagebuilder-n-2",
                 "warnings": [],
                 "registryUrl": "https://gitlab.com/sylva-projects/sylva-core/-/raw/release-1.4/charts/sylva-units/values.yaml",
                 "currentVersion": "0.4.18",
                 "fixedVersion": "0.4.18"
               }
             ],
             "matchStrings": [
               "\\s+# renovate: custom datasource registryUrl=(?<registryUrl>.*) depName=(?<depName>.*)? datasource=(?<datasource>.*)[\\w\\W]*?\\s*tag:\\s*(?<currentValue>\\d+\\.\\d+\\.\\d+)"
             ],
             "versioningTemplate": "loose",
             "packageFile": "charts/sylva-units/values.yaml"
           }

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

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 Nov 18, 2025 by Loic Nicolle

Track sylva_diskimagebuilder_version and sylva_kiwi_imagebuilder_version from previous release with renovate

What does this MR do and why?

Related reference(s)

Test coverage

CI configuration

Global config for deployment pipelines

Merge request reports