The implementation of CDEvents is use case driven. We focus on a few use cases that demonstrate the business value of interoperability in the CI/CD space and for each of them we identify a target architecture, its logical building blocks and a set of software components that can be used to implement it.
Some of the software required is part of the CDEvents project and other is external. All proposed implementation focus exclusively on open source software components. Commercial software that implements standard protocols like CDEvents can be slotted in to replace or complement the open source software adopted by the CDEvents Implementation WG.
CDEvents use cases may apply to two personas: open source project communities and organizations doing in-house software development. The requirements and design of the implementation vary based on the persona and are documented in the use-case specific document.
- Enhance Security Posture through Automation
- Improve Developer Experience through Consistency and Visibility (TBD)
- Drive Efficiency through DevOps Metrics (TBD)
TBD - Describe various type of event producers: tools native, via tool plugin, via external adapter, via external watcher
TBD - Adapter and plugins
CDEvents provides SDKs for various programming languages. The Implementation WG focusses on providing consistency across the various SDKs to simplify adoption.