add support for sylva-library to tools/deps-project-tool.py
sylva-library repo wasn't known by this tool, this MR fixes it
Tests
Tested with:
tools/deps-project-tool.py --check-wrong-tags --include sylva-library
processing 1 projects...
sylva-projects/sylva-elements/helm-charts/sylva-library ...
used: 0.3.5
next: 0.4.0
checking 0.3.* tags
File "/home/teom7365/projets/sylva/sylva-core/tools/deps-project-tool.py", line 401, in <module>
main()
File "/home/teom7365/projets/sylva/sylva-core/tools/deps-project-tool.py", line 397, in main
process_repos(gl, options, gitlab_project)
File "/home/teom7365/projets/sylva/sylva-core/tools/deps-project-tool.py", line 281, in process_repos
raise Exception(f"tag {tag.name} is not on branch '{branch_name}'")
Exception: tag 0.3.6 is not on branch 'release-0.3'
tools/deps-project-tool.py --include sylva-library --base-protected-branches
processing 1 projects...
sylva-projects/sylva-elements/helm-charts/sylva-library ...
used: 0.3.5
would have created branch protection rule for 'release-*.*' (use --commit to realize)
next: 0.4.0
tools/deps-project-tool.py --include sylva-library --tags-new-release --commit
processing 1 projects...
sylva-projects/sylva-elements/helm-charts/sylva-library ...
used: 0.3.5
next: 0.4.0
created protected tag rule '0.4.*'
tag 0.4.0 already exists (and is on 'main')
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
|
|
| Node OS |
ubuntu, suse
|
|
| Deployment Options |
light-deploy, dev-sources, ha, misc, maxsurge-0, logging, no-logging
|
|
| Pipeline Scenarios | Available scenario list and description |
-
🎬 preview☁️ capd🚀 kadm🐧 ubuntu -
🎬 preview☁️ capo🚀 rke2🐧 suse -
🎬 preview☁️ capm3🚀 rke2🐧 ubuntu -
☁️ capd🚀 kadm🛠️ light-deploy🐧 ubuntu -
☁️ capd🚀 rke2🛠️ light-deploy🐧 suse -
☁️ capo🚀 rke2🐧 suse -
☁️ capo🚀 kadm🐧 ubuntu -
☁️ capo🚀 rke2🎬 rolling-update🛠️ ha🐧 ubuntu -
☁️ capo🚀 kadm🎬 wkld-k8s-upgrade🐧 ubuntu -
☁️ capo🚀 rke2🎬 rolling-update-no-wkld🛠️ ha🐧 suse -
☁️ capo🚀 rke2🎬 sylva-upgrade-from-1.4.x🛠️ ha🐧 ubuntu -
☁️ capo🚀 rke2🎬 sylva-upgrade-from-1.4.x🛠️ ha,misc🐧 ubuntu -
☁️ capo🚀 rke2🛠️ ha,misc🐧 ubuntu -
☁️ capm3🚀 rke2🐧 suse -
☁️ capm3🚀 kadm🐧 ubuntu -
☁️ capm3🚀 kadm🎬 rolling-update-no-wkld🛠️ ha,misc🐧 ubuntu -
☁️ capm3🚀 rke2🎬 wkld-k8s-upgrade🛠️ ha🐧 suse -
☁️ capm3🚀 kadm🎬 rolling-update🛠️ ha🐧 ubuntu -
☁️ capm3🚀 rke2🎬 sylva-upgrade-from-1.4.x🛠️ ha🐧 suse -
☁️ capm3🚀 rke2🛠️ misc,ha🐧 suse -
☁️ capm3🚀 rke2🎬 sylva-upgrade-from-1.4.x🛠️ ha,misc🐧 suse -
☁️ capm3🚀 kadm🎬 rolling-update🛠️ ha🐧 suse -
☁️ capm3🚀 ck8s🎬 no-wkld🛠️ light-deploy🐧 ubuntu
Global config for deployment pipelines
-
autorun pipelines -
allow failure on pipelines -
record sylvactl events
Notes:
- Enabling
autorunwill make deployment pipelines to be run automatically without human interaction - Disabling
allow failurewill make deployment pipelines mandatory for pipeline success. - if both
autorunandallow failureare 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.