SonaQube :- Community Edition Version 7.7 (build 23042)
sonar-scanner-3.3.0.1492-linux
sonar-lua-plugin-1.0.jar
I am trying to run SonarQube for Lua project. And I want anyalze the Lua code.
I have installed sonar-lua-plugin-1.0.jar and sonar-scanner-3.3.0.1492-linux. And i tried to run sonar-scanner.
I am able to see Bugs, Vulnerablities, code-smells and duplications but i am not able to get code coverage for that.
I tried to add source and tests in sonar-project.properties file and tried again same issue is there.
I don’t believe the author of the Lua plugin did anything specific for coverage. However, you might be able to generate a coverage report and convert it to the Generic Coverage format.
Hi Ann,
we are using lua plugin and have created generic coverage reports as well as the generic execution reports and since we have changed to SonarQube 7.7 (coming from SonarQube 6.x) these two reports are no longer working.
Do you have a guess what could be the cause?
Hi, we use busted to run tests and luacov for coverage reports.
The tests reports have to be converted to generic execution format to be used in SonarQube.
Can you point me on how you’ve converted test reports to generic execution format used in SonarQube? Also, how you used luacov.stats.out in SonarQube?
Thanks. I’m asking because sonar-lua plugin is outdated and cannot be used in newer SonarQube versions. There is a plugin https://github.com/britzl/luacov-cobertura, which generates cobertura output from luacov. Maybe this can be used in SonarQube?
Hi Ann, I’ve made a small tiny project trying to find the problem with the lua issue.
I could manage to load lua in my environment with 7.3 but no longer with 7.8.
I could provide a tar ball of the tiny project if it would help.
When I look at sonarqube Plugin Version Matrix, I see that lua is no longer marked a compatible.
What does this mean?
What is the incompatibility your developers found?
A few months before we remove deprecated APIs, the developers will usually do a sweep to see what Marketplace plugins are using those APIs to give them one final notification. Then when they drop the APIs we have a list of the plugins that have just lost compatibility and those plugins get marked incompatible starting with the next release.
What the specific API in question is, I couldn’t tell you.
in addition the following two files contain the log from sonar-scanner (slightly modified by reducing the time stamp) to give you as much information as possible. sonar-7-3.log.no-ts.txt (21.4 KB) sonar-7-8.log.no-ts.txt (25.3 KB)
sorry, asking again, but from the Documentation I understood the for all languages the “Generic Execution” format is working out of the bos without any language specific parts.
And this is what we are doing with the two xml files.