Test build for #2302

SUSE · Feb 20, 2025 · 6a0bd92 · 6a0bd92
1 parent b678b53
commit 6a0bd92
Show file tree

Hide file tree

Showing 4 changed files with 10 additions and 10 deletions.
diff --git a/helm-image/Dockerfile b/helm-image/Dockerfile
@@ -17,11 +17,11 @@
 #!ExclusiveArch: aarch64 ppc64le s390x x86_64
 #!BuildTag: suse/helm:%%helm_version%%-%RELEASE%
 #!BuildTag: suse/helm:%%helm_version%%
-#!BuildTag: suse/helm:3.16
+#!BuildTag: suse/helm:3.17
 #!BuildTag: suse/helm:3
 #!BuildTag: suse/helm:latest
-#!BuildName: suse-helm-3.16
-#!BuildVersion: 15.6.3.16
+#!BuildName: suse-helm
+#!BuildVersion: 15.6.3.17
 #!BuildRelease: 35
 FROM registry.suse.com/bci/bci-micro:15.6 AS target
 FROM suse/sle15:15.6 AS builder
@@ -34,7 +34,7 @@ RUN set -euo pipefail; \
 # sanity check that the version from the tag is equal to the version of helm that we expect
 RUN set -euo pipefail; \
     [ "$(rpm --root /target -q --qf '%{version}' helm | \
-    cut -d '.' -f -2)" = "3.16" ]
+    cut -d '.' -f -2)" = "3.17" ]
 FROM registry.suse.com/bci/bci-micro:15.6
 COPY --from=builder /target /
 # Define labels according to https://en.opensuse.org/Building_derived_containers

diff --git a/helm-image/README.md b/helm-image/README.md
@@ -14,13 +14,13 @@
 To run Helm, use the following command:
 
 ```ShellSession
-$ podman run --rm -it  registry.suse.com/suse/helm:3.16 <helm-sub-command>
+$ podman run --rm -it  registry.suse.com/suse/helm:3.17 <helm-sub-command>
 ```
 
 For instance, to display the Helm version, run:
 ```ShellSession
-$ podman run --rm -it registry.suse.com/suse/helm:3.16 version --template='{{.Version}}'
-v3.16
+$ podman run --rm -it registry.suse.com/suse/helm:3.17 version --template='{{.Version}}'
+v3.17
 ```
 
 Refer to the full list of Helm commands, flags and environment variables, in the [official Helm documentation](https://helm.sh/docs/helm/helm/).
@@ -33,7 +33,7 @@ For a comprehensive guide on getting started with Helm, refer to the [official H
 To interact with a Kubernetes cluster, mount the Kubernetes configuration file (`kubeconfig`) from the container host into the container (use the `--net=host` flag to allow the container to use the host’s network):
 
 ```ShellSession
-$ podman run --rm -it --net=host -v /path/to/kubeconfig:/root/.kube/config:Z registry.suse.com/suse/helm:3.16
+$ podman run --rm -it --net=host -v /path/to/kubeconfig:/root/.kube/config:Z registry.suse.com/suse/helm:3.17
 ```
 
 ## Licensing

diff --git a/rmt-server-image/Dockerfile b/rmt-server-image/Dockerfile
@@ -19,7 +19,7 @@
 #!BuildTag: suse/rmt-server:%%rmt_version%%
 #!BuildTag: suse/rmt-server:2
 #!BuildTag: suse/rmt-server:latest
-#!BuildName: suse-rmt-server-2
+#!BuildName: suse-rmt-server
 #!BuildVersion: 15.6.2
 #!BuildRelease: 35
 FROM registry.suse.com/bci/bci-base:15.6

diff --git a/spack-image/Dockerfile b/spack-image/Dockerfile
@@ -19,7 +19,7 @@
 #!BuildTag: bci/spack:0.23.0
 #!BuildTag: bci/spack:0.23
 #!BuildTag: bci/spack:latest
-#!BuildName: bci-spack-0.23
+#!BuildName: bci-spack
 #!BuildVersion: 15.6.0.23
 FROM registry.suse.com/bci/bci-base:15.6