Software Delivery Agent
No items found.
On-demand Webinar
On-demand Webinar

How To Architect a CI/CD Pipeline That Really Scales | Harness Resource

DevOps and platform engineering teams often believe they’ve solved scalability with “push-button” onboarding. However, tools that clone templates, such as internal developer portals, merely automate the creation of technical debt. The moment a pipeline is copied, it drifts. Six months later, making an update across 100 services means managing 100 separate pull requests — or convincing 100 teams to make a change. In this session, our host Chris Pirillo welcomed Harness’ Eric Minick and Choice Hotels’ Stephen Cihak for a spirited discussion on why copying CI/CD templates creates technical debt and leads to operational paralysis (the “scaffolding trap”). Watch now and you’ll also learn why the future of DevOps scaling isn’t about copying YAML; it’s about inheriting it.

Published
March 10, 2026

Guide on its way

Check your inbox — your playbook is ready.

You're all set

Check your inbox — your download is on the way.

Redirect link
No items found.
Redirect link

What you'll learn

Key Takeaways

Downstream Tasks Consume Engineering Time

Testing, security scanning, and triaging take up 50 to 70 percent of an engineering organization's time. This bottleneck limits the downstream benefits of modern AI coding assistants.

Cloning Pipeline Templates Creates Technical Debt

Providing developers with cookie-cutter pipelines to copy leads to massive configuration drift. One organization ended up with 2,800 different pipelines for just a few hundred applications.

Pipeline Drift Threatens Security and Compliance

When teams manually edit cloned pipelines, they often alter thresholds or skip critical tests. This makes it nearly impossible to audit security practices or enforce standard deployments.

Use Referenced Templates Instead of Clones

Architect pipelines using a copy-by-reference approach rather than copying by value. This allows platform teams to update a central template and distribute changes in a controlled manner.

Implement Version Control for Pipeline Templates

Versioned templates allow teams to remain on older pipelines if they are not ready for immediate changes. Platform engineers can then use backend reporting to track template adoption.