DevOps CI/CD System Development
Budget: ₹12,500 – ₹37,500 INR
I want a DevOps CI/CD system with the following capabilities:
Code Management (Developer Actions)
Developers can perform standard Git operations:
Push
Pull
Checkout
Work diff (view differences)
All code changes should go to the development (Dev) cloud server.
Admin Permissions & Code Review
As an admin, I should be able to:
Control which developers are allowed to check in code.
Review and approve/reject check-ins before they are merged into the Dev server.
Environment Promotion Flow
Once approved, the code should be promoted through the following pipeline:
Dev → QA → Production
Admin should have the ability to control when and how code is moved from one environment to another.
Rollback & Version Control
The system must support reverting deployments to a specific date and time.
Complete logs of all deployments and rollbacks should be maintained.
Server Management
If a server crashes, the system should:
Automatically log the incident.
Send notifications to the admin/team.
Provide a one-click option to restart the server.
Logging & Monitoring
Detailed logs should be available for:
Developer commits/check-ins.
Code promotions (Dev → QA → Prod).
Rollbacks.
Server crashes and restarts.
Monitoring dashboards for server health and deployment status.
Essentially, this will be a centralized CI/CD pipeline with access control, approval workflows, rollback capabilities, server monitoring, and crash recovery.
Code Management (Developer Actions)
Developers can perform standard Git operations:
Push
Pull
Checkout
Work diff (view differences)
All code changes should go to the development (Dev) cloud server.
Admin Permissions & Code Review
As an admin, I should be able to:
Control which developers are allowed to check in code.
Review and approve/reject check-ins before they are merged into the Dev server.
Environment Promotion Flow
Once approved, the code should be promoted through the following pipeline:
Dev → QA → Production
Admin should have the ability to control when and how code is moved from one environment to another.
Rollback & Version Control
The system must support reverting deployments to a specific date and time.
Complete logs of all deployments and rollbacks should be maintained.
Server Management
If a server crashes, the system should:
Automatically log the incident.
Send notifications to the admin/team.
Provide a one-click option to restart the server.
Logging & Monitoring
Detailed logs should be available for:
Developer commits/check-ins.
Code promotions (Dev → QA → Prod).
Rollbacks.
Server crashes and restarts.
Monitoring dashboards for server health and deployment status.
Essentially, this will be a centralized CI/CD pipeline with access control, approval workflows, rollback capabilities, server monitoring, and crash recovery.