1. Overview
This document outlines the proposed deployment responsibility separation and CI/CD workflow between TokenMinds and the Client.
The goal is to ensure:
- A clear separation of responsibilities between development (CI) and deployment (CD)
- A flexible integration with the client’s existing infrastructure
- A consistent, reliable build process for all environments
2. Responsibility Separation
| Area |
Responsible Party |
Description |
| Continuous Integration (CI) |
TokenMinds |
Build, test, containerize, and publish Docker images to the Container Registry (CR). |
| Continuous Deployment (CD) |
Clent |
Deploy the container images from CR to staging/production environments according to their infrastructure setup. |
3. TokenMinds – CI Responsibilities
TokenMinds will handle the following:
- Implement CI Pipeline
- Automated build process triggered by changes to the
main branch.
- Containerization using Docker.
- Containerization
- Define Dockerfile and necessary configurations.
- Ensure the application is self-contained and environment-agnostic.
- Image Publishing
- Push built Docker images to the client’s Container Registry (CR).
- Use Git commit SHA as the staging image tag.
- Use Git tag (e.g.,
v1.0.0) for production images.
- Branching Strategy
- Trunk-based development using
main as the trunk branch.
- Each merge to
main triggers an image build and push to CR.
- Production releases are triggered via Git tags.
4. Client – CD Responsibilities
The KhanBank team will handle the deployment and infrastructure management:
- Pull Images from CR
- Retrieve the built and tagged Docker images from the registry.