[HAP-940] Conan executable not found when running Jenkins as a service Created: 19/Jun/17  Updated: 29/Jun/17  Resolved: 29/Jun/17

Status: Resolved
Project: Jenkins Artifactory Plug-in
Component/s: Common
Affects Version/s: None
Fix Version/s: 2.12.0

Type: Bug Priority: High
Reporter: Yahav Itzhak Assignee: Yahav Itzhak
Resolution: Fixed Votes: 0
Labels: None


 Description   

Conan executable is in /usr/local/bin, which is not in the standard PATH.
PATH argument doesn't injected to the Jenkins service. As a result, Jenkins pipeline can't execute binaries like 'conan' which are not in the Jenkins service local PATH.



 Comments   
Comment by Ankush Chadha [ 19/Jun/17 ]

Shouldn't this be treated as maven or any other build/packaging framework where the client side is responsible to do the installation?
These tools should be installed on the jenkins slaves on the fly; or have them pre-installed and use labels to identify what all slaves are responsible to build C++ projects.

https://github.com/JFrogDev/soldev/tree/openshiftHA/openshiftHA/project_examples/cpp-conan/jenkins-slave-cpp-conan

https://github.com/JFrogDev/soldev/blob/openshiftHA/openshiftHA/project_examples/cpp-conan/jenkins-slave-cpp-conan/Dockerfile

Ankush

Generated at Sun Nov 17 20:26:40 UTC 2019 using JIRA 7.6.16#76018-sha1:9ed376192612a49536ac834c64177a0fed6290f5.