Hello, I've recently hit a limit with the code insights API where only a max of 10 reports can be displayed next on an open PR. I didn't see anything like this in the docs here:
https://support.atlassian.com/bitbucket-cloud/docs/code-insights/ or here
https://developer.atlassian.com/cloud/bitbucket/rest/api-group-reports/#api-repositories-workspace-repo-slug-commit-commit-reports-reportid-put,
they mention there can only be 10 elements per report but nothing about the number of reports themselves.
Is there anyway to increase this limit? My use case is reporting build status from Jenkins in a monorepo and would regularly see over 10 reports being generated.
Hello @Shail ,
and welcome to the Community!
The reports are actually attached to a particular commit, and the number of reports is indeed limited to 10 reports per commit. The pull request page will show the reports associated with the last commit that was pushed to the source branch of the pull request.
One alternative to add more information is to use Annotations within the report, as each report can have up to 1000 annotations. This might help you convey the necessary details without exceeding the report limit.
I have raised a request with our documentation team to specifically call out the limitation of 10 reports per commit, as it seems this was not clearly documented.
If you'd be interested, I can also raise a feature request to consider increasing those limits. Please let me know if that would be helpful for your use case.
Thank you, @Shail !
Patrik S
Thanks for the response Patrik!
Yeah my workaround will probably be to consolidate similar reports together, instead of code coverage and static analysis per service just a general code coverage report instead for example.
And yes I'd be interested in a feature request, 10 reports per commit seems like a low limit, especially in a monorepo structure like I mentioned so I'd imagine this will effect others as well, as bitbucket's pipelines and reporting features become more utilized.
Thanks again @Patrik S ,
Shail
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Shail ,
You're very welcome.
Indeed consolidating some reports together might be a good workaround for this situation.
Having said that, I've raised a feature request with our engineering team to raise that limit:
Feel free to add your Vote to that feature so it helps our product managers to understand the interest. You can also post a comment with your use-case and what would be fair number of reports per commit for your scenario.
Last, by setting yourself as a watcher in that feature, you'll get notified by of any future updates.
Thank you, @Shail !
Patrik S
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.