Browse categories
Explore
Fiverr Pro
English
$
USD
I will set up a ci cd pipeline with github actions, gitlab ci or jenkins
About this Gig
Deploying by hand works right up until the day it doesn't. Someone forgets a step, the wrong branch goes out, and nobody is quite sure what is running in production.
I build the pipeline that removes that whole class of problem, in the tool you already use.
What you get:
Pipeline as code, committed to your repo: build, test, artifact, deploy
Secrets handled through the platform's secret store, never hardcoded
Docker image build and push to Docker Hub, ECR, GHCR or your own registry
Staging or UAT environment, with a controlled promotion to production
A rollback path that works, and a runbook so anyone on the team can use it
Works with GitHub Actions, GitLab CI, Jenkins, Bitbucket Pipelines or CircleCI, deploying to AWS, a VPS, Kubernetes or a PaaS. Monorepos, several services and self-hosted runners are all fine.
About me: 15+ years in production systems, currently CTO at Globalnexo, specialized in DevOps and DevSecOps. I run GitLab CE with self-hosted runners every day, and I spent years as the developer waiting on the pipeline... so I build ones people actually want to use.
Tools:
Docker
•
GitLab
•
Jenkins
•
GitHub
•
CircleCI
Frameworks:
Terraform
•
Ansible
Programming language:
Bash
•
JavaScript
•
Python
Expertise:
Installation
•
Development
•
Configuration
Other DevOps Engineering Services I Offer
FAQ
Which CI tool should I use?
Usually the one attached to where your code already lives. GitHub Actions for GitHub, GitLab CI for GitLab. Jenkins makes sense when you need self-hosted control. I will tell you honestly which fits.
Do you need access to our repository and servers?
Yes, a branch in the repo and a deploy target. I work on a branch and nothing reaches production until you approve the run. A test repo first is fine if you prefer.
