Remove the Hurdles of Non-interoperability in Your CI/CD Workfl...
summary
Jenkins emits events via a CloudEvents plugin for Jenkins (a GSoC project) and a proof‑of‑concept routes those events through a Knative broker and trigger into Tekton TaskRuns, proving format standardization removes adapter code. The remaining blocker is vocabulary: Jenkins build/job names stay tool‑specific so consumers still need tool semantics. The next step is adopting a CDEvents standard to standardize event types so multi‑tool CI/CD becomes truly loosely coupled and scalable.
AI-written summary · about
chapters (8)
- 0:00Start
- 1:24The Different Types of Interoperability
- 3:39Standardization & Event-Driven Approach
- 4:54Level 1 - Standardizing the format of Events
- 8:38Our Journey with the CloudEvents Plugin
- 11:06Looking into Events Supported by the Plugin
- 16:28Answering Our Questions Finding the Missing Link
- 18:35Level - Standardizing the Type of Events
related talks
20mEnhancing Interoperability in CI/CD Workflows Using CDEvents
30mThe Road to Interoperability in Cloud Native Continuous Deli...
17mLet's Work Together! : CI/CD Interoperability using CDEvents
19mAdopting CDEvents and Embracing Interoperability
29mJenkins 2022 and Beyond?
25mBridging the Gap with Tekton-client-plugin for Jenkins
45mCloud native CI/CD: Tekton vs Jenkins X
35mJenkins Scaling and Organization for an Efficient CI