Is your feature request related to a problem? Please describe.
Have a slew of CI jobs that build and published to an Artifactory instance. Sometimes the connection may fail when publishing (e.g. network issue) and the default retry event occurs (default, 3 times with a 0 interval).
If I want to update the retry approach, such as waiting ~10 seconds per retry, I have to update each project to use this.
Describe the solution you'd like to see
It would be nice if there was an environment variable to configure the retry defaults. For example:
JFROG_CLI_RETRIESJFROG_CLI_RETRY_WAIT_TIME
Where CLI takes priority, then environment then default (assuming that's why jf uses now).
Describe alternatives you've considered
Was thinking of adding a generic CI argument for all jf calls, but seemed to be the same time/effort as the original issue.
Additional context
n/a
Is your feature request related to a problem? Please describe.
Have a slew of CI jobs that build and published to an Artifactory instance. Sometimes the connection may fail when publishing (e.g. network issue) and the default retry event occurs (default, 3 times with a 0 interval).
If I want to update the retry approach, such as waiting ~10 seconds per retry, I have to update each project to use this.
Describe the solution you'd like to see
It would be nice if there was an environment variable to configure the retry defaults. For example:
JFROG_CLI_RETRIESJFROG_CLI_RETRY_WAIT_TIMEWhere CLI takes priority, then environment then default (assuming that's why
jfuses now).Describe alternatives you've considered
Was thinking of adding a generic CI argument for all
jfcalls, but seemed to be the same time/effort as the original issue.Additional context
n/a