At OpsLevel we believe Service Ownership is the foundation for scaling a modern software engineering organization. But ownership is much more than Team X owns service Y. It also includes important work like:
- Defining, documenting, and prioritizing your best practices
- Measuring services against those standards
- Doing the work to improve services and meet (or exceed!) standards
Git Repositories & Ownership
Standards or best practices can cover any facet of a service’s design, configuration, or performance and be measured from a variety of angles. But an ideal starting point is a service’s source code.
With scalable access to all your git repos, it’s simple to validate things like:
- Do all my services have codeowners files?
That’s why we’re excited to add Azure DevOps to our roster of git integrations; we want more teams to have access to all the benefits of embracing Service Ownership.
With the new integration, teams using Azure DevOps (ADO) Git repositories have access to a suite of powerful functionality for cataloging, measuring, and improving their services. Teams can:
- Use YAML files in repos to control service ownership and associated metadata
- Review all repos from your integrated ADO account in OpsLevel and assign repo ownership
- Verify that all services in OpsLevel are mapped to a repository
- Confirm that repositories are using branch protection on their default branch
- Search repos for the presence of specified files and strings
Configuring the ADO git integration requires just a few clicks in OpsLevel, though we do suggest using a service account as the integrating user. You can find the full instructions for setting up the integration in our docs.
If you're ready to get serious about Service Ownership, try out the power of our git integrations by requesting your custom OpsLevel demo today.