You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If CLI is installed in /usr/bin the plugin detects that special case and uses $HOME/.jfrog or some other configurable directory that is writable by the Jenkins user.
If there is a way to properly handle this case, it should be documented where the environment variable should be set. (Setting it in the Jenkinsfile does not appear to work)
JFrog plugin version
1.5.1
JFrog CLI version
2.59.1
Operating system type and version
RHEL 8.10
JFrog Artifactory version
No response
JFrog Xray version
No response
The text was updated successfully, but these errors were encountered:
Describe the bug
We have JFrog plugin installed via RPM in /usr/bin.
When doing this, the JFrog plugin uses /usr/bin/../dependencies.
Current behavior
My Jenkinsfile has the following environment variables defined:
Running "env" in my Jenkins job yields the following output:
Relevant change:
https://github.com/jfrog/jenkins-jfrog-plugin/pull/8/files#diff-66ba23408a67cc0911950d1cad200bd33db1837503e2e5aa8c5aba38ece516ea
Reproduction steps
Use jfrog cli from RPM installed in /usr/bin
Expected behavior
If CLI is installed in /usr/bin the plugin detects that special case and uses $HOME/.jfrog or some other configurable directory that is writable by the Jenkins user.
If there is a way to properly handle this case, it should be documented where the environment variable should be set. (Setting it in the Jenkinsfile does not appear to work)
JFrog plugin version
1.5.1
JFrog CLI version
2.59.1
Operating system type and version
RHEL 8.10
JFrog Artifactory version
No response
JFrog Xray version
No response
The text was updated successfully, but these errors were encountered: