Describe the bug
The pipeline job fails as a result of trying to authenticate to Artifactory while adding the configuration (first step in any use of jfrog-cli).
Current behavior
During peak times, there is a lot of network traffic going to Artifactory. Busy times causes the pipeline to break as the jfrog-cli isn't able to add a configuration, let alone upload artifacts. Requests times out and job fails with the following message(s):
14:38:35 [Warn] failed while trying to check latest JFrog CLI version: json: unknown field "url"
14:38:56 [Warn] (Attempt 1) - Failure occurred while sending GET request to https://xxx.failsafe.net/artifactory/api/security/encryptedPassword: Get "https://xxx.failsafe.net/artifactory/api/security/encryptedPassword": dial tcp x.x.x.x:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
14:38:56 [Info] executor timeout after 0 attempts with 0 milliseconds wait intervals
14:38:56 [Info] Trace ID for JFrog Platform logs: 63ca8631078243da
14:38:56 [Error] The following error was received while trying to encrypt your password: Get "https://xxx.failsafe.net/artifactory/api/security/encryptedPassword": dial tcp x.x.x.x:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Found unhandled java.lang.RuntimeException exception:
Couldn't execute 'jf' command. RuntimeException: Running 'jf' command failed with exit code 1
PluginClassLoader for jfrog//io.jenkins.plugins.jfrog.JfStep$Execution.run(JfStep.java:134)
PluginClassLoader for jfrog//io.jenkins.plugins.jfrog.JfStep$Execution.run(JfStep.java:92)
PluginClassLoader for workflow-step-api//org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:49)
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:572)
java.base/java.util.concurrent.FutureTask.run(FutureTask.java:317)
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
java.base/java.lang.Thread.run(Thread.java:1583)
Reproduction steps
I guess you could try to stress your Artifactory instance with a bunch of small upload/download requests, some larger some smaller. Then run your pipeline as you normally would.
Expected behavior
This should not occur, jfrog plugin should retry that operation and it should succeed.
JFrog plugin version
1.6.1
JFrog CLI version
2.91.0
Operating system type and version
Windows 2K22
JFrog Artifactory version
7.133.10
JFrog Xray version
N/A
Describe the bug
The pipeline job fails as a result of trying to authenticate to Artifactory while adding the configuration (first step in any use of jfrog-cli).
Current behavior
During peak times, there is a lot of network traffic going to Artifactory. Busy times causes the pipeline to break as the jfrog-cli isn't able to add a configuration, let alone upload artifacts. Requests times out and job fails with the following message(s):
Reproduction steps
I guess you could try to stress your Artifactory instance with a bunch of small upload/download requests, some larger some smaller. Then run your pipeline as you normally would.
Expected behavior
This should not occur, jfrog plugin should retry that operation and it should succeed.
JFrog plugin version
1.6.1
JFrog CLI version
2.91.0
Operating system type and version
Windows 2K22
JFrog Artifactory version
7.133.10
JFrog Xray version
N/A