Request to support environment variable configuration for retries/retryWaitTime
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 68/100
Research direction
Start by locating the retry and retryWaitTime handling in the Go CLI and trace how command-line values and defaults are selected. Add support for JFROG_CLI_RETRIES and JFROG_CLI_RETRY_WAIT_TIME with CLI values taking precedence over environment values and defaults, then run the relevant retry tests or add coverage for the precedence behavior.
Written by the indexing model from the issue text.
Description
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
- Dominant language
- Go
- Stars
- 595
- Forks
- 307
- Avg merge
- 4d 17h
- Merged PRs (30d)
- 17
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from jfrog/jfrog-cli
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
feature request
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
-
question
Difficulty 3/5 1-2 days Newbie friendliness 52/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 1/5 Under an hour Newbie friendliness 84/100
-
enhancement needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
kind/cleanup
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
kubernetes-sigs/kueue#15947 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
sympozium-ai/sympozium#627 ·