Add Bitbucket Code Insights reports and annotations for PipelineRun results

[blochjared92]

Feature request

Add support for publishing Pipelines as Code / Tekton PipelineRun results to Bitbucket Data Center Code Insights.

For Bitbucket Data Center, Pipelines as Code currently creates commit/build statuses, but it does not provide a rich PR review experience comparable to GitHub Checks. This makes it harder for developers to understand why a PipelineRun failed without leaving Bitbucket and opening the OpenShift/Tekton logs.

Bitbucket Data Center has a native Code Insights API/UI that supports reports and annotations on pull requests. This would be a good fit for surfacing PipelineRun status, failed tasks, links to logs, and eventually file/line-level findings directly in the PR.

Requested behavior:

• For Bitbucket Data Center pull request events, publish or update a Code Insights report for each relevant PipelineRun.
• Include high-level PipelineRun information in the report, such as:
  • PipelineRun name
  • status/result
  • failed task or tasks
  • duration
  • namespace
  • commit SHA
  • link to the OpenShift/Tekton PipelineRun logs or console view
• Continue creating Bitbucket build/commit statuses so existing merge checks still work.
• Optionally support Code Insights annotations for task output that can be mapped to a file and line number.
• When line-level mapping is not available, publish the failure as report-level details or a file-level annotation where possible.
• Avoid noisy PR comments by default. If comments are supported, make them optional and limited to a concise failure summary plus a link to full logs.
• Document the behavior and configuration for Bitbucket Data Center users.

This would give Bitbucket Data Center users a more native PR experience, similar in value to GitHub Checks, without requiring a separate Bitbucket plugin or custom external integration.

Use case

We use Pipelines as Code with Tekton/OpenShift Pipelines and Bitbucket Data Center.

When a developer opens or updates a pull request, PAC starts a Tekton PipelineRun. If the build, test, lint, or scan task fails, the developer currently has to leave Bitbucket, find the PipelineRun in OpenShift/Tekton, inspect logs, and then map the failure back to the code manually.

This is especially painful during PR review because the reviewer sees that the build failed, but not why it failed or where the relevant issue is in the code.

A richer Bitbucket Data Center integration would improve the workflow:

1. Developer opens a PR.
2. PAC runs the Tekton PipelineRun.
3. Bitbucket build status shows pass/fail for merge checks.
4. A Bitbucket Code Insights report appears on the PR with PipelineRun summary details.
5. If a task produces file/line-level errors, annotations appear in the PR diff near the changed code.
6. The developer can understand and fix the issue without leaving the PR unless they need full logs.