tkobayas commented on code in PR #6049:
URL: 
https://github.com/apache/incubator-kie-drools/pull/6049#discussion_r1721548035


##########
.ci/jenkins/Jenkinsfile.weekly.deploy:
##########
@@ -91,7 +91,8 @@ pipeline {
                     withCredentials([usernamePassword(credentialsId: 
env.MAVEN_REPO_CREDS_ID, usernameVariable: 'REPOSITORY_USER', passwordVariable: 
'REPOSITORY_TOKEN')]) {
                         def installOrDeploy
                         if (shouldDeployToRepository()) {
-                            installOrDeploy = "deploy -DdeployAtEnd 
-Dapache.repository.username=${REPOSITORY_USER} 
-Dapache.repository.password=${REPOSITORY_TOKEN} -DretryFailedDeploymentCount=5"
+                            installOrDeploy = "deploy -DdeployAtEnd 
-Dapache.repository.username=${REPOSITORY_USER} 
-Dapache.repository.password=${REPOSITORY_TOKEN} 
-DretryFailedDeploymentCount=5" +
+                                    " -Dhttp.socket.timeout=300000 
-Dhttp.connection.timeout=300000"

Review Comment:
   As far as I understand, `maven-deploy-plugin` doesn't specify timeout 
values, so the default values seem to be 60 sec. 
https://stackoverflow.com/questions/9734384/default-timeout-for-httpcomponent-client
   
   Indeed, there was a log telling that the timeout happened within 2 minutes.
   ```
   [2024-08-04T04:32:56.568Z] [INFO] Retrying deployment attempt 4 of 5
   [2024-08-04T04:34:17.465Z] [WARNING] Failed to upload checksum to 
org/drools/drools-ruleunits/999-20240804-SNAPSHOT/drools-ruleunits-999-20240804-20240804.030311-1.pom.sha1
   [2024-08-04T04:34:17.465Z] org.apache.http.client.HttpResponseException: 
status code: 408, reason phrase: Request Timeout (408)
   ```
   
   So I set 300 sec this time. I hope we can see an observable difference.
   



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to