-
Story
-
Resolution: Done
-
Undefined
-
None
-
None
-
None
-
False
-
-
False
-
-
-
DP Sprint 27
Currently base-images readme [1] talks about tags convention for the main branch. But we do not have any docs around the tag format in a branch. For example early access releases branch also need tags.
Here is the suggestions for the tags for the branches.
v3.4-EA2.2026030501 or if we need specific cuda build for 3.4 EA it should be cuda-v3.4-EA2.2026030501. These formats will work with the existing ON-CEL expressions in the repo.
pipelinesascode.tekton.dev/on-cel-expression: |
event == "push" && (
target_branch.startsWith("refs/tags/v") ||
target_branch.startsWith("refs/tags/cuda-v") ||
Below are the existing docs in the Readme which needs to be updated.
Tag naming conventions The git tag should use the naming convention vYYYYMMDD##, e.g. v2025042801 for a release on Apr 28, 2025. All components: vYYYYMMDD## - builds all base image variants (CPU, CUDA, ROCm, Spyre, TPU) (e.g. v2025112501) Specific components: <component>-vYYYYMMDD## - builds only the specified component: cpu-vYYYYMMDD## - CPU variant only (e.g. cpu-v2025112601) cuda-vYYYYMMDD## - CUDA variant only rocm-vYYYYMMDD## - ROCm variant only spyre-vYYYYMMDD## - Spyre variant only (e.g. spyre-v2025110601) tpu-vYYYYMMDD## - TPU variant only gaudi-vYYYYMMDD## - Gaudi variant only (currently disabled) The ## suffix is a two-digit sequence number starting at 01, incremented if multiple releases are needed on the same day.
[1]https://gitlab.com/redhat/rhel-ai/core/base-images/app#tag-naming-conventions
