Project Name
80+ Pipeline Rewrites Eliminated for a Multi-Cloud Retail Platform With Dagger on OCI and AWS
A large North American retail and eCommerce enterprise running OCI and AWS had built its entire CI/CD estate on Jenkins – 80+ Groovy DSL pipelines tightly coupled to a single vendor. Any migration to GitHub Actions or OCI DevOps meant rewriting every pipeline from scratch, estimated at months of effort. Independent teams across multiple business units had each evolved their own pipeline conventions with no standards, no local testing, and no unified deployment visibility. Applying its AI-First approach, Ksolves introduced Dagger to make all pipeline logic portable, vendor-neutral, and locally testable – without touching a single line of application code.
- Complete CI Vendor Lock-In: All 80+ pipelines were written in Jenkins-specific Groovy DSL with no abstraction layer - every CI/CD decision was a long-term commitment to a single vendor, blocking any migration to modern tooling.
- Pipeline Rewrites as the Migration Tax: Any move away from Jenkins required full rewrites of every pipeline - estimated at months of engineering effort and significant regression risk across both OCI and AWS production workloads.
- No Local Pipeline Testing Capability: Jenkins Groovy DSL pipelines could only be validated by running them in CI - creating 5-10 minute feedback loops per iteration, frequent broken builds, and wasted developer time waiting for remote execution.
- Fragmented Multi-Cloud Artifact Management: OCI workloads pushed images to OCIR while AWS workloads targeted ECR with no unified pipeline logic - each cloud had its own bespoke push-and-deploy sequence, doubling maintenance overhead.
- Zero Deployment Visibility Across Clouds: No unified portal existed to show deployment status, pipeline health, or service ownership across OCI and AWS simultaneously - teams context-switched between multiple dashboards to understand system state.
- Inconsistent Pipeline Standards Across Teams: Each business unit had evolved its own pipeline conventions - security controls inconsistently applied, cross-team collaboration difficult, and organisation-wide pipeline audits structurally impossible.
Ksolves redesigned the CI/CD layer around Dagger as the portable pipeline engine and Backstage as the unified developer portal. One principle: all pipeline logic expressed once in TypeScript, executed identically on Jenkins, GitHub Actions, or OCI DevOps - cloud context injected at runtime, never hardcoded.
- Dagger TypeScript SDK for Provider-Agnostic Pipelines: All CI/CD logic - build, test, image push, and deploy - rewritten in TypeScript using the Dagger SDK. Pipelines run identically on Jenkins, GitHub Actions, and OCI DevOps without modification, eliminating vendor lock-in for all 80+ pipelines in a single refactor.
- Local Pipeline Execution and Testing: Dagger's container-native execution model allows every pipeline to be run and validated locally before any remote CI trigger - developers catch failures on their workstations in under 30 seconds rather than waiting for a remote Jenkins executor.
- Backstage as Unified Multi-Cloud Portal: Backstage was deployed as the single pane of glass showing real-time deployment status, pipeline health, and service ownership across both OCI and AWS - replacing fragmented per-cloud dashboards with one authoritative view.
- Unified Artifact Pipeline to OCIR and ECR: The same Dagger pipeline logic handles container image builds and pushes to both OCIR (for OKE workloads) and ECR (for EKS workloads) - cloud target determined by runtime context, not duplicated pipeline definitions.
- OCI DevOps Integration as First-Class Target: OCI DevOps was integrated alongside Jenkins and GitHub Actions, enabling teams running OCI-native workloads to trigger the same Dagger pipelines through OCI's native CI/CD service without any pipeline changes
Technology Stack
| Category | Technology |
|---|---|
| CI/CD | Dagger (TypeScript SDK) |
| Platform | Backstage |
| Infrastructure | OCI DevOps |
| Registry | OCI Container Registry + AWS ECR |
| Compute | Kubernetes (OKE + EKS) |
- 80+ Pipeline Rewrites Eliminated: All pipelines run identically on Jenkins, GitHub Actions, or OCI DevOps via Dagger TypeScript SDK - provider switch now requires a runtime config update, not a re-engineering project.
- CI Migration Cut From Months to Days: Provider changes require only a runtime configuration update - CI tooling decisions made on merit, not migration cost.
- Feedback Loop Cut to Under 30 Seconds: Dagger's local execution surfaces pipeline failures on developer workstations in under 30 seconds, replacing 5-10 minute remote CI loops.
- Unified Deployment Visibility Across OCI and AWS: Backstage delivers real-time deployment status and pipeline health across both clouds in one portal - fragmented dashboard context-switching eliminated.
- Artifact Pipeline Standardised Across OCIR and ECR: Single Dagger pipeline logic targets both OCIR and ECR - halving artifact maintenance effort and eliminating duplicate push-and-deploy sequences per cloud.
“For the first time, our teams can switch CI tools without anyone losing sleep over pipeline rewrites – Dagger gave us back our ability to make infrastructure choices based on merit, not migration cost.”
– VP of Engineering.
A large retail enterprise locked into 80+ Jenkins Groovy DSL pipelines across OCI and AWS was freed from CI vendor lock-in through Ksolves’ DevOps consulting services. Dagger TypeScript SDK now expresses all pipeline logic once – running identically on Jenkins, GitHub Actions, and OCI DevOps without rewrites. CI migration dropped from months to days, local feedback loops cut to under 30 seconds, and Backstage unified deployment visibility across both clouds. Any future CI tooling change is now a configuration update, not a re-engineering project.
CI/CD Pipelines Holding Your Cloud Strategy Hostage to a Single Vendor
