Azure DevOps Multi-Stage Pipeline
Budget: ₹600 – ₹1,500 INR
I am modernising our CI/CD workflow and need a specialist who can shape a clean, reliable multi-stage pipeline inside Azure DevOps. The core work sits firmly in the Pipelines service, but you will also be threading together the wider toolchain that supports our stack:
• Source lives in GitHub and will continue to be the single source of truth.
• Infrastructure is declared in Terraform.
• Deployments target a Kubernetes cluster.
Your first task is to design and script the end-to-end pipeline (build, test, security scan, Terraform plan/apply, container image build, and Kubernetes deploy) using Azure DevOps YAML. Re-usable templates, variables, and environments should keep everything tidy and portable. I expect gated stages, clear approvals, and meaningful release notes generated automatically.
Once the core flow is in place, hand-off must include:
1. Complete YAML in our repo, clearly commented.
2. Pipeline-level documentation that shows where to plug in new microservices or environments.
3. A short screen-share walkthrough so the team can operate and extend it confidently.
Quality bar: the pipeline should run green on the first try after you turn it over, rebuild a feature branch in under ten minutes, and roll back cleanly if any deployment stage fails.
Let me know your relevant Azure DevOps pipeline projects, especially if they involved Terraform and Kubernetes. If you can demonstrate previous work linking GitHub Actions or other runners into Azure DevOps environments, that’s a plus—our long-term roadmap may include hybrid orchestration.
Looking forward to collaborating and getting this automated the right way the first time.
• Source lives in GitHub and will continue to be the single source of truth.
• Infrastructure is declared in Terraform.
• Deployments target a Kubernetes cluster.
Your first task is to design and script the end-to-end pipeline (build, test, security scan, Terraform plan/apply, container image build, and Kubernetes deploy) using Azure DevOps YAML. Re-usable templates, variables, and environments should keep everything tidy and portable. I expect gated stages, clear approvals, and meaningful release notes generated automatically.
Once the core flow is in place, hand-off must include:
1. Complete YAML in our repo, clearly commented.
2. Pipeline-level documentation that shows where to plug in new microservices or environments.
3. A short screen-share walkthrough so the team can operate and extend it confidently.
Quality bar: the pipeline should run green on the first try after you turn it over, rebuild a feature branch in under ten minutes, and roll back cleanly if any deployment stage fails.
Let me know your relevant Azure DevOps pipeline projects, especially if they involved Terraform and Kubernetes. If you can demonstrate previous work linking GitHub Actions or other runners into Azure DevOps environments, that’s a plus—our long-term roadmap may include hybrid orchestration.
Looking forward to collaborating and getting this automated the right way the first time.
Related categories:
Kubernetes
DevOps
GitHub
Automation
Microservices
Terraform
CI/CD
Containerization