@@ -48,6 +48,7 @@ The CNB template uses some global configuration used throughout all jobs.
| `builder-image` / `CNB_BUILDER_IMAGE` | The CNB builder image used to build your application image<br/>_depending on your needs, [choose the most appropriate one](https://paketo.io/docs/concepts/builders/#what-paketo-builders-are-available)_ | `docker.io/paketobuildpacks/builder-jammy-base:latest`<br/>[](https://to-be-continuous.gitlab.io/doc/secu/trivy-CNB_BUILDER_IMAGE) |
| `platform-api` / `CNB_PLATFORM_API` | The CNB [platform API version](https://github.com/buildpacks/spec/blob/main/platform.md#platform-api-version) | `0.14` |
| `source-date-epoch-enabled` / `CNB_SOURCE_DATE_EPOCH_ENABLED` | Enable setting [`SOURCE_DATE_EPOCH` to configure image create time](https://github.com/buildpacks/rfcs/blob/main/text/0103-source-date-epoch.md) based on Git commit date. | `false` |
The CNB template allows building multiple images in parallel (for instance with multiple separate application source code base directories in your repository).
This feature can be enabled using the [parallel matrix jobs](https://docs.gitlab.com/ee/ci/yaml/#parallelmatrix)
pattern at the `.cnb-base` job level.
:information: Output variables namespacing can be ensured by using the `CNB_ARTIFACTS_NAMESPACE` variable.
Here is the example of the `.gitlab-ci.yml` file for a project building 2 application images:
"description":"Defines extra tags to publish the _release_ image\n\nSupports capturing group references from `$CNB_RELEASE_EXTRA_TAGS_PATTERN` (ex: `latest \\g<major>.\\g<minor> \\g<major>`)",
"advanced":true
},
{
"name":"CNB_ARTIFACTS_NAMESPACE",
"description":"Output artifacts namespace _(only required when building multiple images)_",