--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/eefe0887-c933-4541-aab3-1f286c04b371n%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/8c629824-db3d-404f-9845-a95f14f4849dn%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/1cfaf8d9-b011-4249-9540-168f075d4049n%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/d268e9b6-727c-4697-87e1-a9df64781a60n%40googlegroups.com.
Am 26.03.2021 um 11:28 schrieb jesus fernandez <jesusfern...@gmail.com>:Thanks for the replies but how woud the command be then? something like this cppcheck "E:/Source" --force — enable=all — inconclusive — xml — xml-version=2 . > cppcheck.xm
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/233a664a-9d1c-4833-b6e7-29f959b374cfn%40googlegroups.com.
You probably need something like this:
cppcheck --xml-version=2 --enable=all <path1> <path2> 2>samplecppcheck.xml
https://stackoverflow.com/questions/10611011/cannot-generate-xml-output-from-cppcheck
cppcheck is a pain from command line, the command line was an after though, they screw big time. I stop using it just for that reason, the CLI is not matching the GUI and the results are unpredictable in case of errors. The fact that it requires the redirection of std_err, just that show a bad design from people who doesn’t give a damn about CLI. I strongly recommend you find something else to do your static analysis into your CI.
Jérôme Godbout, B. Ing.
Software / Firmware Team Lead
O: (418) 682-3636 ext.: 114
C: (581) 777-0050
godb...@dimonoff.com
1015 Avenue Wilfrid-Pelletier,
Québec, QC G1W 0C4, 4e étage
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/A54FBCD1-C520-4109-9A5B-4CEECF0B8F4B%40gmail.com.
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-users/IEyGzpdo1-8/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/QB1PR01MB3844C2C47704FA2735D7C364CD619%40QB1PR01MB3844.CANPRD01.PROD.OUTLOOK.COM.
I cannot recommend it since I haven’t try it out, but you can find many over here:
https://en.wikipedia.org/wiki/List_of_tools_for_static_code_analysis#C,_C++
Moved to Visual Studio since we already have the license. But this depends on your needs. Cppcheck work great with GUI but the CLI is retarded.
This is the command I used into Jenkins when I did tried cppcheck:
String cmd = "cppcheck --project=${scriptConfig} --xml --xml-version=2 ${otherOptions} 2> ${outputXml}";
The first –xml should not be necessary according to the doc, but I added it anyway just in case, but failure is unreliable like you did discover.
When I got time I would give https://codechecker.readthedocs.io/en/latest/ a go to see what it can do, it use llvm/clang with a better CLI
Jérôme Godbout, B. Ing.
Software / Firmware Team Lead
O: (418) 682-3636 ext.: 114
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CALZFchfsYmyonc-MPWFFt3yR_C_fSLs5VbO%2B%2B99jL9ZRVyxX%3Dg%40mail.gmail.com.