Skip to content

Conversation

@parth5012
Copy link

📌 Description

This PR implements the Continuous Integration (CI) pipeline requested in #41 to automate the containerization of the MicroForge application.

What does this PR do?

  • Added Root Dockerfile: Created a comprehensive Multi-Stage Dockerfile that defines build targets for all 5 microservices (auth, frontend, login, metadata, notification).
  • GitHub Actions Workflow: Implemented .github/workflows/docker-publish.yml using a Matrix Strategy. This allows all 5 services to be built and pushed in parallel jobs.
  • Dynamic Tagging: Configured the pipeline to tag images with semantic versions (e.g., v1.0.0), latest, and the Git commit SHA for traceability.

Why is this change needed?
Previously, builds and pushes were manual. This automation ensures that every change to the master branch is automatically verified, built, and deployed to the Docker Registry without human intervention.


🔗 Related Issue

Fixes #41


🛠️ Type of Change

Please mark the relevant option:

  • Documentation update
  • Bug fix
  • New feature
  • Refactor
  • Configuration / DevOps change
  • Other (please explain)

🧪 How Was This Tested?

Describe how you verified your changes:

  • Docker Compose runs successfully
  • Frontend loads correctly
  • Service builds without errors
  • Documentation renders correctly
  • Manual testing (Verified workflow execution on a fork/feature branch)

📸 Screenshots (if applicable)

No UI changes. Workflow logs confirm successful parallel builds:
image


✅ Checklist

Please confirm the following:

  • My code follows the project structure
  • I tested my changes locally (and via CI triggers)
  • I linked the relevant issue
  • I kept this PR focused and minimal
  • I am open to feedback and changes

📝 Additional Notes

⚠️ Critical Setup for Maintainers:

For this pipeline to function correctly after merging, the project admin must add the following Repository Secrets in Settings > Secrets and variables > Actions:

  1. DOCKER_USERNAME: The Docker Hub username.
  2. DOCKER_PASSWORD: The Docker Hub password (or Access Token).

@github-actions
Copy link

github-actions bot commented Jan 9, 2026

🚫 Pull Request Policy Violation

Hi @parth5012, thanks for your contribution!

Direct PRs to the master branch are not allowed. Please close this PR and target the stage branch instead for review.

@github-actions github-actions bot closed this Jan 9, 2026
@parth5012 parth5012 deleted the SetupDocker branch January 11, 2026 13:21
@parth5012 parth5012 restored the SetupDocker branch January 11, 2026 13:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Enhancement] [CI] Setup Docker Build & Push Pipeline for Master Branch

1 participant