You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The CC_EXTENSIONS field under 'Constants' has been removed and when using Bazel 6.0.0 with the Bazel sonar extension, it fails with the missing field exception.
Along with CC_EXTENSIONS, Coverage.getOnlyTheseCcSources has been removed.
Since my project doesn't have any C++ projects and is only Java, I tried just removing all of this C++ code and that resulted in Sonar failing to parse the output file due to "Look at SonarQube documentation to know the expected XML format. ParseError at [row,col]:[1,1]". Not sure if it was something I did on my end or if something about the C++ code made this not happen before. I need to investigate further when I have some time.
The text was updated successfully, but these errors were encountered:
I've synced the coverage generator Main class from Bazel 6.0.0 in commit 77044ec. The version in this repo is just a direct copy of the upstream one, but which calls the local SQ-format output printer instead of the lcov one (unfortunately it's not a configurable extension point).
This should fix the issue - let me know if you're still having problems when using this revision.
The
CC_EXTENSIONS
field under 'Constants' has been removed and when using Bazel 6.0.0 with the Bazel sonar extension, it fails with the missing field exception.Along with CC_EXTENSIONS, Coverage.getOnlyTheseCcSources has been removed.
Since my project doesn't have any C++ projects and is only Java, I tried just removing all of this C++ code and that resulted in Sonar failing to parse the output file due to "Look at SonarQube documentation to know the expected XML format. ParseError at [row,col]:[1,1]". Not sure if it was something I did on my end or if something about the C++ code made this not happen before. I need to investigate further when I have some time.
The text was updated successfully, but these errors were encountered: