Browse categories
Explore
Fiverr Pro
English
$
USD
I will build gitlab cicd pipeline with automated testing, deployment
Cloud DevOps Engineer
I am a Cloud DevOps Engineer with a strong foundation in designing and optimizing cloud infrastructures, automation, and building CI/CD pipelines. I have experience in reducing deployment complexities...
About this Gig
Tired of deploying by hand or waiting on slow, flaky releases? I build CI/CD pipelines that test, package and deploy your code automatically.
I'm a Certified Kubernetes Administrator (CKA) with 5 years of DevOps/SRE experience. In production I've improved deployment frequency by 30%, raised test coverage to 70%, and added post-deployment validation checks that reduced manual intervention and failed releases.
What I can build:
- GitLab CI pipelines: build, test, scan, deploy
- Docker image builds and pushes to a registry (for example AWS ECR)
- Automated deployments to AWS (EC2, EKS) and Kubernetes with Helm
- GitOps with ArgoCD
- Infrastructure deployment pipelines (Terraform, CloudFormation/CDK)
- Post-deployment health checks
What you get: working pipeline files in your repo, documentation, and a short walkthrough so your team can maintain it.
Message me before ordering with your repo host, language and deployment target, and I'll recommend the right package.
Tools:
Docker
•
GitLab
•
GitHub
•
Cloud Formation
Frameworks:
Terraform
•
Ansible
Programming language:
Bash
•
Java
•
Python
Expertise:
Development
•
Configuration
Other DevOps Engineering Services I Offer
FAQ
Do you need access to my repository?
Limited access to the repo is enough, or I can build the pipeline from sample files and send you the files to add. Never send me passwords or production secrets. We'll use CI variables instead.
What is ArgoCD, and do I need it?
ArgoCD deploys to Kubernetes automatically from Git, so what's in Git is what's running. It's useful for Kubernetes teams. If you don't use Kubernetes, the Basic or Standard package is enough.
Will you write my tests?
No. I wire your existing tests into the pipeline and can set up coverage reporting. Writing new tests is a separate job.
How do you handle secrets?
Through CI/CD variables and secret managers, never in the repo.
What if my project is bigger than a package covers?
Message me and I'll send a custom offer.
