From CDEvents To Actions: Designing the Workflow Conductor
summary
Conduit converts CDEvents into actionable orchestration by mapping normalized events from Jenkins, GitHub Actions, CircleCI, Argo CD, Datadog, PagerDuty, Jira, Slack and Zendesk to workflow segments (build, test, deploy, canary, rollback). It runs event listeners, a matcher, segment contract loader, router and DSL executor, maintains state and observability, and enforces policies that can pause deployments, create Jira tickets, send Slack alerts or trigger automated rollbacks. Event authenticity uses DSSE signatures and CDEvents from the CDF project provide the standard format.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:47Siloed CI/CD problems
- 3:35What are CDEvents and why they matter
- 5:43Event orchestration vs workflows
- 8:53Workflow segments and contracts
- 11:48Conduit orchestration platform
- 14:33Conduit industry impact
- 15:56Event-driven SDLC importance
- 16:59Q&A
related talks
22mCDEvents as Catalyst to Innovation in CI/CD Ecosystem
30mCI/CD Observability: Standardizing with CDEvents
08mBuilding a Future of Greater Interoperability in CI/CD with CDEvents
19mAdopting CDEvents and Embracing Interoperability
06mEvents in CI/CD
20mEnhancing Interoperability in CI/CD Workflows Using CDEvents
18mCDEvents in Tekton: The path to a more interoperable CI/CD system
01h 04mCDEvents Project Summit