search

LabVIEW-DCAF / buildsystem

Location of reusable build script files, groovy libraries, and other infrastructure items needed for DCAF build servers
Apache License 2.0
18 stars 7 forks source link

Run VI Analyzer missing in shared library #43

Open sr33-multics opened 6 years ago

sr33-multics commented 6 years ago

runVIAnalyzer.groovy missing from shared library.

pollockm commented 6 years ago

Hello!

You’re right, it’s not there. I’ll add it in today. Thanks for reporting the issue!

sr33-multics commented 6 years ago

Here is the code.

def call(configFilePath, lv_version){ echo 'Run VI Analyzer tests' bat "labview-cli --kill --lv-ver ${lv_version} \"L:\\run-vi-analyzer.vi\" -- \"${configFilePath}\" \"build_temp\\VIA_results.xml\" \"${WORKSPACE}\"" echo 'Junit' junit allowEmptyResults: true, testResults: "build_temp\\VIA_results.xml" }

pollockm commented 6 years ago

Results are inoperable in Junit format, as far as I know. There is another package that I'm tweaking that will get rolled in soon to allow VI Analyzer results to be consumed by the Checkstyle plugin (https://github.com/LabVIEW-DCAF/VIA-Checkstyle).

The end result will look a little different than your comment above.

pollockm commented 6 years ago

We had some community discussion on this here: https://forums.ni.com/t5/Continuous-Integration/VI-Analyzer-Results-gt-Checkstyle-Format/gpm-p/3743386 , which led to going the checkstyle route rather than Junit.