{"id":17325,"date":"2026-09-01T17:07:56","date_gmt":"2026-09-01T17:07:56","guid":{"rendered":"https:\/\/dmsretail.com\/RetailNews\/from-release-days-to-continuous-promotion-building-the-foundation-for-agentic-promotions\/"},"modified":"2026-09-01T17:07:56","modified_gmt":"2026-09-01T17:07:56","slug":"from-release-days-to-continuous-promotion-building-the-foundation-for-agentic-promotions","status":"publish","type":"post","link":"https:\/\/dmsretail.com\/RetailNews\/from-release-days-to-continuous-promotion-building-the-foundation-for-agentic-promotions\/","title":{"rendered":"From Release Days to Continuous Promotion: Building the Foundation for Agentic Promotions"},"content":{"rendered":"

\"Retail<\/a><\/p>
\n<\/p>\n

\n

Learn how ThousandEyes<\/span> transformed its deployment culture from manual, fragmented release cycles to a centralized delivery model\u2014using GitOps alongside standardized automation, policy-driven controls, and shared operational practices. The result is a unified, auditable path to production that strengthens digital resilience and developer productivity by reducing manual handoffs, accelerating delivery, and enabling faster detection and remediation. Now being adopted by other Cisco business units, the model establishes the foundation for agentic promotions.<\/em><\/p>\n

In the world of software engineering, \u201crelease day\u201d is often a source of friction. It implies manual checklists, coordination meetings, and a heavy reliance on institutional knowledge. At Cisco <\/span>ThousandEyes<\/span>, we realized that this bottleneck was incompatible with our goal of delivering rapid, reliable innovation. We needed to stop treating releases as distinct events and start treating them as a continuous, automated, and governed business process.<\/span>\u00a0<\/span><\/p>\n

The Challenge: Fragmented Visibility<\/span>\u00a0<\/span><\/h2>\n

Our previous release model treated environment promotions as largely manual processes. Release state was scattered across GitHub deployments, approval threads, and institutional knowledge, making it difficult to establish a single source of truth. While controls such as freeze windows and deployment reviews existed, they were applied inconsistently across teams and workflows.<\/span>\u00a0<\/span><\/p>\n

For ThousandEyes, the delivery challenge was not just speed; it was <\/span>digital resilience<\/span><\/b>: we lacked a unified, auditable path from staging to production, and assessment controls were fragmented across multiple systems.<\/span> This limited our ability to continuously evaluate risk, enforce governance consistently, and rapidly identify and remediate issues throughout the software delivery lifecycle. <\/span>Continuous promotion<\/span><\/b> directly addresses that gap by making promotion state, policy, and readiness criteria explicit, centralized, and continuously enforceable, rather than dependent on release-day coordination.<\/span>\u00a0<\/span><\/p>\n

The Solution: a centralized CD control plane with an enforceable verification layer<\/span>\u00a0<\/span><\/h2>\n

To modernize software delivery at scale, Cisco <\/span>ThousandEyes<\/span> built <\/span>OdysseyCD<\/span><\/b>, our internal continuous delivery (CD) platform, on <\/span>Kargo<\/span>. OdysseyCD provides a continuous promotion framework that simplifies the developer experience while strengthening delivery governance. Reusable verification gates and standardized promotion patterns let teams and Cisco business units apply consistent release-readiness checks and controls without rebuilding promotion workflows for each application, environment, or organization.<\/span>\u00a0<\/span><\/p>\n

We focused on three core pillars:<\/span>\u00a0<\/span><\/p>\n