Code integrations (read-only)

Code integrations give Sleuth read-only access to your code repositories, allowing Sleuth to analyze your pull requests, commits, files and authors to provide a meaningful and clear view of the changes you make in code when you deploy.

Integration	Type	Additional info...
Azure DevOps	Code Deployment	Can be used a change source.
Bitbucket	Code Deployment	Can be used a change source.
GitHub	Code Deployment	Can be used as a change source.
GitLab	Code Deployment	Can be used as a change source.
Custom Git	Code Deployment	Can be used as a change source.
Terraform Cloud	Code Deployment	Auto register deploys via a webhook

Version Control Workflow

Sleuth encourages and works best with a trunk-based development workflow. As observed by Accelerate:

Developing off trunk rather than on long-lived branches is correlated with higher delivery performance

Scaled trunk-based development

If your teams create short-lived branches that are merged into a core branch (trunk, main, master) at least daily then you're working consistent with commonly accepted continuous integration best practices. Sleuth is an excellent tool for your team.

Strict trunk-based development caveats

If your team is small or nimble enough to commit directly to one branch, more granular data may not be available or relevant (e.g., review time and review lag time in change lead time) depending on your process and provider. However, Sleuth will still surface the important metrics to help your team succeed in its software delivery optimization goals.