I'll build fast, reliable CI/CD pipelines that your developers can trust, or fix and migrate the ones you have.
What you get
Pipelines in GitLab CI, Jenkins (as code) or GitHub Actions: build, test, scan and deploy
Reusable templates so every service follows the same path
Container image builds with vulnerability scanning (Trivy) and secret scanning (Gitleaks)
GitOps deployments with Argo CD (or Flux) and promotion between environments
Self-hosted runners on Kubernetes (EKS Spot) to cut cost, if it fits
Documentation so your team can maintain it
Migrations
Jenkins to GitLab CI or GitHub Actions, done in phases without breaking releases
At Deutsche Telekom Digital Labs I led the migration of 300+ Jenkins pipelines to self-hosted GitLab CI runners on EKS, cutting pipeline overhead by about 70%. At Avizva I ran Jenkins as code for 90+ pipelines with shared libraries.
I'll build fast, reliable CI/CD pipelines that your developers can trust, or fix and migrate the ones you have.
What you get
Pipelines in GitLab CI, Jenkins (as code) or GitHub Actions: build, test, scan and deploy
Reusable templates so every service follows the same path
Container image builds with vulnerability scanning (Trivy) and secret scanning (Gitleaks)
GitOps deployments with Argo CD (or Flux) and promotion between environments
Self-hosted runners on Kubernetes (EKS Spot) to cut cost, if it fits
Documentation so your team can maintain it
Migrations
Jenkins to GitLab CI or GitHub Actions, done in phases without breaking releases
At Deutsche Telekom Digital Labs I led the migration of 300+ Jenkins pipelines to self-hosted GitLab CI runners on EKS, cutting pipeline overhead by about 70%. At Avizva I ran Jenkins as code for 90+ pipelines with shared libraries.