Introducing the first open platform for software engineering data
The data necessary to understand the entire software delivery process is increasingly fragmented. To ship a single feature, a team may take advantage of 10+ tools, from project management, to version control, CI/CD, feature flags and more.
At Code Climate, we’ve learned that combining data from different sources enables higher-level insights. For example, PagerDuty can tell you how often your developers are getting woken up—but it can’t tell you the impact on innovation. Adding Jira data enables you to understand the delays those incidents have on feature initiatives.
To unlock the full value from these data sources, we need:
- A standard language for understanding DevOps concepts
- A simple way to connect to the wide array of engineering tools
And that’s exactly what we’re excited to be announcing today.
We’re launching the Code Climate Engineering Data Platform with:
- A standard Data Schema, representing 50+ common software development units, like epics, pull requests, builds, incidents and more
- An open Connector specification for integrating with DevOps tools
- A SDK (and scaffolding template) to enable anyone to rapidly build new Connectors
Each Connector requests data from a DevOps tool’s API and outputs a set of records conforming to the data schema. Here’s how it works:
To kick things off, we’re open sourcing Connector reference implementation for PagerDuty, CircleCI and Codecov, all written in Node.js.
We believe that the future of DevOps data is open, and today, we’re taking the first step towards making this vision a reality.
The Code Climate Community
We created the first extensible ecosystem for code quality four years ago. There are now 50+ static analysis and test coverage tools available, developed by thousands of community contributors, benefiting millions of engineers. Companies like GitLab have used it as the foundation for their code quality solutions.
With the new Engineering Data Platform, we’re helping the broader software development community build the first open standards for all engineering and DevOps data. We’d love your feedback or contributions on everything we are announcing today (it’s all in draft form!).
Here’s how you can get involved:
- Explore our Data Schema and Specification docs on GitHub
- Join the conversation on Slack with hundreds of community contributors
- Subscribe to our Developer Program mailing list to stay up-to-date
We look forward to building the next generation of Velocity and Quality features using this new, open standard. We’re also excited to see how others will take advantage of the Code Climate Engineering Data Platform to build products and tools we haven’t even thought of yet.
Trending from Code Climate
1.
How to Navigate New Technology Expectations in Software Engineering Leadership
Rapid advancements in AI, No-Code/Low-Code, and SEI platforms are outpaced only by the evolving expectations they face. Learn how engineering leaders can take actionable steps to address new technology challenges.
2.
Mapping Engineering Goals to Business Outcomes
Understanding how engineering activities impact business objectives enables engineering leaders to make informed strategic decisions, keep teams aligned, advocate for resources, or communicate successes.
3.
Unlocking Efficiency: Optimizing Pull Request Reviews for Enterprise Engineering Teams
As engineering teams grow, so can the complexity of the code review process. From understanding industry benchmarks to improving alignment across teams, this article outlines strategies that large engineering organizations can use to optimize Review Cycles.
Get articles like this in your inbox.
Get more articles just like these delivered straight to your inbox
Stay up to date on the latest insights for data-driven engineering leaders.