Is your feature request related to a problem? Please describe.
I would like to be able to run jf directly from its docker container instead of having to install it on the agent. We don't directly run builds on the node but rather run them on Docker containers with the required tooling. This means that if we want to use this plugin we will need to install it on all of our docker images which will be a pain to manage. We would like to be able to run it directly from the docker container as suggested in https://jfrog.com/help/r/jfrog-cli/jfrog-cli-v2-jf-installers (see Docker section).
This setup also prevents us from using the automated installation methods unfortunately.
Describe the solution you'd like to see
jf can be run from Docker instead of being installed
Describe alternatives you've considered
The alternative I can see for my use-case are:
Not use this plugin and configure jf manually
Create a jf wrapper on the path that forwards the call to Docker jf
I would like to avoid both solution and have it directly implemented in the plugin if possible. If not, solution 2 seems like a good enough workaround
Is your feature request related to a problem? Please describe.
I would like to be able to run jf directly from its docker container instead of having to install it on the agent. We don't directly run builds on the node but rather run them on Docker containers with the required tooling. This means that if we want to use this plugin we will need to install it on all of our docker images which will be a pain to manage. We would like to be able to run it directly from the docker container as suggested in https://jfrog.com/help/r/jfrog-cli/jfrog-cli-v2-jf-installers (see Docker section).
This setup also prevents us from using the automated installation methods unfortunately.
Describe the solution you'd like to see
jf can be run from Docker instead of being installed
Describe alternatives you've considered
The alternative I can see for my use-case are:
I would like to avoid both solution and have it directly implemented in the plugin if possible. If not, solution 2 seems like a good enough workaround
Additional context
No response