DeployMate

Release Workflow — From Source Code to Production

Git Repository
GitHub · GitLab · Bitbucket
or
Azure DevOps
Repos · Pipelines · Artifacts
2
Bank of Build Servers
DeployMate pulls the latest source code and distributes the build across a pool of dedicated build servers. Each server compiles the code, runs tests, and packages the release artifact — automatically and in parallel.
.NET Core & .NET Framework
Angular
React
Background Services
3
Successful Build → Upload Artifact
Once the build passes all checks, the compiled artifact is packaged and securely uploaded to the DeployMate release store — ready to be pushed to any number of target servers.
4
Push Release to Target Servers
The release is pushed simultaneously to one or many servers. Before deploying the code, DeployMate automatically syncs everything the application needs to run correctly.
Sync Bindings & Port Assignments
Sync SSL Certificates
Sync Configurations
Deploy Release Code
Windows & Linux Servers
IIS Sites & App Pools
5
Verify the Release
DeployMate performs automatic health checks — confirming the application is responding, the SSL certificate is active, the database is reachable, and response times are within acceptable limits.
Deployment Outcome
✓
Success — Release Live
Application is healthy and serving traffic
↩
Failure — Auto Rollback
Previous version instantly restored
7
Run Automated Tests
Once the release is live, DeployMate kicks off a suite of automated tests — functional, integration, and regression — against the running application to validate real-world behaviour.
Automated Test Results
✓
All Tests Passed
Report generated & logged automatically
✕
Tests Failed
Failure report generated for review
Human Review → Promote to Production
A team member reviews the test report and makes the final call. DeployMate provides all the data needed — pass rates, response times, and any failures — to make a confident, informed decision.
✓ Approve & Push to Production ⏸ Hold for Further Review ↩ Rollback & Investigate