Closed larsskj closed 1 year ago
The tool directory on the node does not contain the tool either.
The reason was a missing auto installation of the tool due to CasC (the generated yaml omits the tool installation configuration).
Yes - sorry - this was a mistake on our side.
Let's close this ticket.
Describe the bug
We're experimenting with the new JFrog plugin in order to implement it in our setup.
However, today we learned that it doesn't work on Windows nodes: When a pipeline tries to call
jf.exe
it fails as it tries to executeWe alse found that the environment variable
JFROG_BINARY_PATH
has the valuenull
.Current behavior
See above.
Reproduction steps
Setup the plugin as recommended with the JFrog CLI installed as a global tool - and try running any command involving
jf
on a Windows node.Expected behavior
That it works like it does on Linux.
JFrog plugin version
1.0.5
JFrog CLI version
latest as of March 3rd 2023.
Operating system type and version
Jenkins stock Docker image - 2.393 on the master / Windows 10 on node
JFrog Artifactory version
No response
JFrog Xray version
No response