-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[incubator-kie-issues-1444-weekly] drools.weekly-deploy jobs frequent… #6056
[incubator-kie-issues-1444-weekly] drools.weekly-deploy jobs frequent… #6056
Conversation
…ly fail with Request Timeout (408) - Disable parallel put
@@ -92,7 +92,7 @@ pipeline { | |||
def installOrDeploy | |||
if (shouldDeployToRepository()) { | |||
installOrDeploy = "deploy -DdeployAtEnd -Dapache.repository.username=${REPOSITORY_USER} -Dapache.repository.password=${REPOSITORY_TOKEN} -DretryFailedDeploymentCount=5" + | |||
" -Dhttp.socket.timeout=300000 -Dhttp.connection.timeout=300000" | |||
" -Daether.connector.basic.parallelPut=false" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As I wrote in apache/incubator-kie-issues#1444 (comment) , http.socket.timeout
and http.connection.timeout
don't seem to be effective.
"Request Timeout (408)" is generally caused by a slow client request. While testing locally, I found that maven 3.9.6 (= maven-resolver-1.9.18) uses 5 threads for parallel uploading by default. aether.connector.basic.parallelPut=false
makes uploading sequential with single thread. I hope that it makes uploading stable. The entire job may take longer time, but I think it's worth trying.
https://maven.apache.org/components/resolver-archives/resolver-1.9.18/configuration.html
09-01: SUCCESS 3 WARNINGs in the 1st attempt. 2nd attempt successful. (Note:
This change |
…ly fail with Request Timeout (408) (apache#6056) - Disable deployAtEnd
…ly fail with Request Timeout (408) (apache#6056) - Disable parallel put
…ly fail with Request Timeout (408)
Issue: