Jenkins run as his own user by default, check node user or login user you are using. The cppcheck must be into that user env PATH variable.
I work round this to avoid spamming the PATH variable on the machine by doing env config into Jenkins, and I use that env variable to give a full path on each node.
https://<MyJenkinsHost>/computer/<MyNodeName>/configure
Then each node can install or put his binary into a custom path depends on the node. I use the node label to declare his capacity:
That way I run into a node that provide DOXYGEN for example, I then need to resolve the doxygen path with the env variable or if the variable is not present I assume the tool is inside the node current PATH var already (save some time for tool that are install system wide).
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
--
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/04691194-8864-411b-bd34-2ed8e20ab9fan%40googlegroups.com.