
CI/CD setup: from a commit to production without manual steps
We build the pipeline that takes a commit through build, tests and deploy. An image is built once and promoted between environments. Deploys go through GitOps, so production runs what is written in Git, and a rollback is a revert.
When you need this
- 1
Deploys are done over SSH by the one person who knows the commands
- 2
A release takes hours and gets postponed because it is risky
- 3
Builds are slow and the team waits for the pipeline
- 4
Nobody can tell which version runs in production right now
- 5
A failed release cannot be rolled back quickly
What's included
Pipelines
GitHub Actions or GitLab CI workflows: lint, tests, build, deploy. Shared steps move into reusable workflows, so services do not copy each other's YAML.
Image builds
Docker images with multi-stage builds and layer caching, tagged by commit and pushed to a registry. The same image goes to staging and then to production.
GitOps deploys
Argo CD or Flux watches a repository with Helm values and applies it to the cluster. The pipeline changes an image tag in Git and needs no direct access to production.
Rollbacks
A release that fails its health checks does not replace the working version. To return to the previous one, you revert a commit or run one command.
Preview environments
A pull request gets its own temporary environment with a URL. It is removed when the pull request is closed.
Secrets and access
Pipeline secrets are stored encrypted, cloud access uses short-lived OIDC credentials, and production deploys can require an approval.
How the work goes
- 1
Call and access
You show how a release happens today. We get access to the repositories and the current pipelines.
- 2
Plan and price
Pipeline stages, the branch and environment model, where GitOps fits. You get the scope and the price before work starts.
- 3
Build
We start with one service and bring it to production through the new pipeline. Then we repeat it for the others from the same templates.
- 4
Handover or support
Your team gets the workflows, a description of the release process and a rollback instruction. We can stay to maintain runners and pipelines.
Questions
- GitHub Actions
- GitLab CI
- Argo CD
- Flux
- Helm
- Docker
- BuildKit
- Kubernetes
- Terraform
- SOPS
Describe the task — get a plan and a price
Write what you have and what you need. We answer within one business day with questions or a concrete proposal.