From e93806493ad0f50550a792931d90e82071bc18b8 Mon Sep 17 00:00:00 2001 From: Andreas Fink Date: Fri, 11 Jul 2025 11:47:12 +0200 Subject: [PATCH 1/3] add GT4Py as example project using dynamic-image-name --- docs/services/cicd.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/services/cicd.md b/docs/services/cicd.md index 0932d418..50960fb4 100644 --- a/docs/services/cicd.md +++ b/docs/services/cicd.md @@ -463,6 +463,7 @@ If you want only specific artifacts in your job, you should have a look at [depe There is also a building block in the templates, name `.dynamic-image-name`, which you can use to get rid for most of the boilerplate. It is important to note that this building block will export the dynamic name under the hardcoded name `BASE_IMAGE` in the `dotenv` file. +Additionally the variable `DOCKER_TAG`, which is the tag of the image is exported in the `dotenv` file. The jobs would look something like this: ```yaml build base: @@ -485,6 +486,9 @@ build software: `build base` is using additionally the building block `.dynamic-image-name`, while `build software` is unchanged. Have a look at the definition of the block `.dynamic-image-name` in the file [.ci-ext.yml](https://gitlab.com/cscs-ci/recipes/-/blob/master/templates/v2/.ci-ext.yml) for further notes. +!!! example "GT4Py example" + An example using `.dynamic-image-name` in action can be found in the [gt4py repository](https://github.com/GridTools/gt4py/tree/main/ci) + ### Image cleanup Images pushed to [CSCS_REGISTRY_PATH](#ci-variables) are cleaned daily according to the following rules: From ee8f4352b0a3e55f7e673cd6a36b7a1d069bcd4f Mon Sep 17 00:00:00 2001 From: finkandreas Date: Fri, 11 Jul 2025 14:24:51 +0200 Subject: [PATCH 2/3] Update docs/services/cicd.md Co-authored-by: Mikael Simberg --- docs/services/cicd.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/services/cicd.md b/docs/services/cicd.md index 50960fb4..e0d25230 100644 --- a/docs/services/cicd.md +++ b/docs/services/cicd.md @@ -463,7 +463,7 @@ If you want only specific artifacts in your job, you should have a look at [depe There is also a building block in the templates, name `.dynamic-image-name`, which you can use to get rid for most of the boilerplate. It is important to note that this building block will export the dynamic name under the hardcoded name `BASE_IMAGE` in the `dotenv` file. -Additionally the variable `DOCKER_TAG`, which is the tag of the image is exported in the `dotenv` file. +The variable `DOCKER_TAG`, containing the tag of the image, is also exported in the `dotenv` file. The jobs would look something like this: ```yaml build base: From db2711edd20ebea36a767b698fc2728afe596fda Mon Sep 17 00:00:00 2001 From: finkandreas Date: Fri, 11 Jul 2025 14:24:58 +0200 Subject: [PATCH 3/3] Update docs/services/cicd.md Co-authored-by: Mikael Simberg --- docs/services/cicd.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/services/cicd.md b/docs/services/cicd.md index e0d25230..96085832 100644 --- a/docs/services/cicd.md +++ b/docs/services/cicd.md @@ -487,7 +487,7 @@ build software: Have a look at the definition of the block `.dynamic-image-name` in the file [.ci-ext.yml](https://gitlab.com/cscs-ci/recipes/-/blob/master/templates/v2/.ci-ext.yml) for further notes. !!! example "GT4Py example" - An example using `.dynamic-image-name` in action can be found in the [gt4py repository](https://github.com/GridTools/gt4py/tree/main/ci) + An example using `.dynamic-image-name` in action can be found in the [gt4py repository](https://github.com/GridTools/gt4py/tree/main/ci). ### Image cleanup Images pushed to [CSCS_REGISTRY_PATH](#ci-variables) are cleaned daily according to the following rules: