Does sonar.javascript.lcov.reportPaths have limitation?

SonarQube Cloud
1

Hi!

I have some questions and i’d appreciate if someone could help!

I’m using sonar.javascript.lcov.reportPaths to send multiple lcov reports by comma separated and i am wondering,

  • if reportPaths have a length limitation which i should take care?
  • if these reports are merged in sonar side?

Thanks!

2

Hi,

Welcome to the community!

I’m not aware of any limits off-hand. And I know some OSes (* cough Windows *) have file path length limits, so you probably want to keep that in mind. Is there a particular reason for the question?

Well… kinda. The data is aggregated, if that’s what you’re asking.

 
Ann

3

Thanks, Ann, for your response!

We have unit and integration tests running with shards. Previously, we used a tool to merge these reports into a single LCOV report before sending it to Sonar. However, due to issues with our third-party tool, we are now trying to send multiple reports as a comma-separated list.

I’m asking because we may need to send at least 15 LCOV reports at once using reportPaths and it can be more in future. If there are any limitations on this property, we’ll need to address them and find a workaround to avoid exceeding the limit.

4

Hi,

Thanks for sharing your use case. Ultimately, these value end up as Java properties, so I double-checked with a quick search that led me to this SO answer

so it is probably safe to assume that the rules are the same as for String:

 
HTH,
Ann

5

Great! Thanks for your quick responses