Bitbucket Code Insights
Lifecycle supports pull request monitoring from the configured default branch to a non-default target branch, such as main to release/v1.0, across supported source control integrations. For Bitbucket Data Center, Lifecycle creates Code Insights reports for these pull requests. The Code Insights report is generated by comparing the policy evaluation report of the pull request's source branch with:
the latest policy evaluation report for the common ancestor commit between the pull request's source and target branches, if such report exists, or
the latest policy evaluation report for the pull request's base commit, which is the head commit of the pull request's target branch at the moment the pull request was created, if such report exists, or
the latest available policy evaluation report for the source control configured default branch.
Learn about Bitbucket's Code Insights from the Atlassian support site.
Prerequisites
Integrating Lifecycle with the Bitbucket Code Insights has prerequisites.
Your IQ Server instance must be configured for Bitbucket SCM
The Bitbucket repository must have a configured default branch and another branch that is used as the pull request source or target.
Code Insight Report Content
A summary of the policy violation information generated by comparing the policy evaluations associated with the pull request’s source and target branches.
A link to the full report in your IQ Server.
Each component that led to a policy violation and a synopsis of which policy has been violated and how.
A link to the file and line number for violations which were introduced as a part of this Pull Request
Annotations in the build file indicating the line which is causing the policy violation
