Pipeline report annotations hiding behind similarly named annotations

[Petrus Hakakoski]

Hello.

I've build a custom pipe to parse the code coverage for our project, but I'm having some issues with the pipeline report annotations.

For this project we have +150 annotations, which does match with the amount under the report, but for some reason it has put in duplicated annotations of certain classes which share a similar names to each other, instead of the actual classes with lower severity level.

Example: lib/database.inc.php was "HIGH", but instead there is 2x  lib/database_log.inc.php which is "CRITICAL".

The annotation externalids all have the report name as the prefix with the later half being SHA1 generated string that comes from the filepath + name so for they should all have unique suffix.

I'm certain that they are being POSTed correctly, as I can see them in the pipeline debug messages AND the correct annotation for the classes is highlighted with the correct severity level in the pull requests view, even tho you can't find that class in the report's  annotations.

Any insight into how to fix this issue?

[Petrus Hakakoski · Accepted solution]

Was found to be a bug, where the Pipeline report annotations aren't being fetch correctly when over 100 due to pagination error https://jira.atlassian.com/browse/BCLOUD-21713

[Patrik S]

Hello @Petrus Hakakoski 

Welcome to Atlassian Community!

Reading through the details you have provided, we'll likely need to access your build logs and pull request to understand the behavior you reported.

Checking our internal tools I've noticed you have access to a workspace in the Standard plan, so in order to further investigate this case, I have created an internal ticket for you using the email of your community account, so you don't have to share this information here.

You should have received an email with a link to the support ticket. Just in case you haven't received it, please feel free to let me know and I can post the ticket URL here. The ticket will be visible only to you and Atlassian staff, no one else can view its contents even if they have the URL.

Thanks, @Petrus Hakakoski .

Kind regards,

Patrik S