-
Notifications
You must be signed in to change notification settings - Fork 105
Open
Labels
bugSomething isn't workingSomething isn't working
Description
Describe the bug
I've placed jf in the runner cache, but the action is still downloading if because jfrog isn't cached.
Debug logs excerpt
##[debug]isExplicit: 2.75.0
##[debug]explicit? true
##[debug]checking cache: /opt/hostedtoolcache/jf/2.75.0/x64
##[debug]Found tool in cache jf 2.75.0 x64
##[debug]isExplicit: 2.75.0
##[debug]explicit? true
##[debug]checking cache: /opt/hostedtoolcache/jfrog/2.75.0/x64
##[debug]not found
Downloading JFrog CLI from https://releases.jfrog.io/artifactory/jfrog-cli/v2/2.75.0/jfrog-cli-linux-amd64/jfrogThe workaround seems to place both jf and jfrog in the cache. but that seems wasteful.
If one tool is found, why do we need the other?
Current behavior
Is download the CLI even though it's found in the cache
Reproduction steps
Place jf in the tools cache eg: /opt/hostedtoolcache/jf/2.75.0/x64 for x64
Expected behavior
if jf is found, don't download jfrog as well
Setup JFrog CLI version
v4.5.11
JFrog CLI version
2.75.0
Workflow operating system type and version
linux
JFrog Artifactory version (if relevant)
No response
JFrog Xray version (if relevant)
No response
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working