Build the mariadb chart.

.woodpecker/mariadb.yaml

@@ -0,0 +1,13 @@
+---
+when:
+  path: "charts/mariadb/**"
+branches:
+  - main
+pipeline:
+  package:
+    image: "docker.io/alpine/helm:latest"
+    secrets: [helm_user, helm_password, helm_repo]
+    commands:
+      - helm plugin install https://github.com/chartmuseum/helm-push
+      - helm repo add therepo $HELM_REPO --username $HELM_USER --password $HELM_PASSWORD
+      - helm cm-push charts/mariadb therepo

charts/mariadb/Chart.yaml

@@ -1,24 +1,6 @@
 apiVersion: v2
 name: mariadb
-description: A Helm chart for Kubernetes
-
-# A chart can be either an 'application' or a 'library' chart.
-#
-# Application charts are a collection of templates that can be packaged into versioned archives
-# to be deployed.
-#
-# Library charts provide useful utilities or functions for the chart developer. They're included as
-# a dependency of application charts to inject those utilities and functions into the rendering
-# pipeline. Library charts do not define any templates and therefore cannot be deployed.
+description: A Helm chart for mariadb
 type: application
-
-# This is the chart version. This version number should be incremented each time you make changes
-# to the chart and its templates, including the app version.
-# Versions are expected to follow Semantic Versioning (https://semver.org/)
 version: 0.1.0
-
-# This is the version number of the application being deployed. This version number should be
-# incremented each time you make changes to the application. Versions are not expected to
-# follow Semantic Versioning. They should reflect the version the application is using.
-# It is recommended to use it with quotes.
 appVersion: "10.6.10"