feat: CI/CD Workflow for Building and Pushing Docker Images

[UtkarshMishra-Microsoft]

Purpose

Configurations Settings

Trigger Conditions:

Runs on pushes and pull requests (for branches: main, dev, demo, hotfix) as well as manually via workflow_dispatch.

Environment Setup:

Uses Ubuntu runners and sets environment variables for Azure Container Registry (ACR) credentials from secrets.

Sets up Docker Buildx

Conditional ACR Login:

The login step executes only if the branch name is one of main, dev, demo, or hotfix, ensuring that pull requests or non-designated branches do not trigger a login.

Dynamic Tagging with Date:

Determines the Docker image tag based on the branch name:

main → latest

dev → dev

demo → demo

hotfix → hotfix

All other branches default to pullrequest-ignore

Additionally, the workflow retrieves the current date (formatted as YYYY-MM-DD) and appends it to the tag, enhancing traceability (e.g., latest-2023-04-02).

Image Build & Optional Push:

Builds three Docker images (ContentProcessor, ContentProcessorAPI, and ContentProcessorWeb) from their respective directories.

After building, each image is pushed to ACR only if the tag is one of the recognized values (e.g., latest-, dev-, etc.). Otherwise, the push is skipped to prevent unintended deployments.

Does this introduce a breaking change?

• Yes
• No

Golden Path Validation

• I have tested the primary workflows (the "golden path") to ensure they function correctly without errors.

Deployment Validation

• I have validated the deployment process successfully and all services are running as expected with this change.

What to Check

Verify that the following are valid

• ...

Other Information

[github-actions]

🎉 This PR is included in version 1.0.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀