CDEvents (https://cdevents.dev/) is a new specification by the CD Foundation which allows exposing useful data about the CI/CD related to builds, failures, time to recovery, time, deployments, and so on.
It's a pretty new (v0.1.0) standard and many projects are just starting to integrate with that, but it'll be a nice one in the future when you can switch the CI/CD pipeline runner system and have the same metrics exposed.
The data then could be transformed into a DORA metrics.
Here is an example study: state of the open-source based on the DORA metrics: https://community.faros.ai/docs/state-of-oss-study that grades OSS projects based on their CI/CD velocity (releases, frequency, failures, builds, deployments, time to resolve bugs, etc).
Eventually, it'll become a widely used standard and it would be nice for BitOps to integrate with that too.
The implementation could be something like configuring a CDEvents backend and send it from the BitOps side.
PoC high-level architecture diagram: https://hackmd.io/@cdfoundation/BklL3MGx9
CDEvents (https://cdevents.dev/) is a new specification by the CD Foundation which allows exposing useful data about the CI/CD related to builds, failures, time to recovery, time, deployments, and so on.
It's a pretty new (v0.1.0) standard and many projects are just starting to integrate with that, but it'll be a nice one in the future when you can switch the CI/CD pipeline runner system and have the same metrics exposed.
The data then could be transformed into a DORA metrics.
Here is why it's important: https://cloud.google.com/blog/products/devops-sre/using-the-four-keys-to-measure-your-devops-performance (https://github.com/GoogleCloudPlatform/fourkeys) as it helps answer how fast-moving and "Elite" is the DevOps team with the metrics and measures. This is good for businesses, enterprises, and any development teams.
Here is an example study: state of the open-source based on the DORA metrics: https://community.faros.ai/docs/state-of-oss-study that grades OSS projects based on their CI/CD velocity (releases, frequency, failures, builds, deployments, time to resolve bugs, etc).
Eventually, it'll become a widely used standard and it would be nice for BitOps to integrate with that too. The implementation could be something like configuring a CDEvents backend and send it from the BitOps side. PoC high-level architecture diagram: https://hackmd.io/@cdfoundation/BklL3MGx9