Refine Docker Image Tagging Strategy to Enhance Stability in Releases

[Fovty]

Issue

Adjustments in Docker Image Tagging and Building Strategy

Problem to Solve

The current Docker build pipeline in the docker-build.yml automatically tags main branch commits with "latest". This practice can lead to unstable versions being tagged as "latest", which are then pulled and deployed by various systems automatically. We need to ensure that only stable, tested versions are marked as "latest".

Affected Product/Feature: Docker image tagging and deployment strategy in the CI/CD pipeline.

Further Details

This issue impacts how our Docker images are built and tagged during CI/CD workflows. Changing this would:

• Ensure only stable releases receive the "latest" tag.
• Prevent the accidental deployment of unstable or development versions in production environments.
• Align our CI/CD practices with common best practices for Docker image management.

Proposal

Modify the GitHub Actions workflow in docker-build.yml:

• Remove the automatic application of the "latest" tag for main branch commits.
• Apply the "latest" tag exclusively when new tags (e.g., release tags) are created.
• Introduce a mechanism to extract the semantic version from the git tag (github.ref) and use it for tagging the Docker image.

Who Can Address the Issue

This issue requires input from the DevOps team with expertise in GitHub Actions and Docker workflows. Knowledge of our current CI/CD processes and tagging conventions will be essential.

Other Links/References

• Originally posted by @puffitos in feat/e2e-test-pipeline #15 (comment)
• Docker official documentation on tags

[Fovty]

Will create a PR as soon as #15 is merged