Skip to content
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

fix: maven staging timeout #1737

Merged
merged 1 commit into from
Sep 24, 2024
Merged

Conversation

iliapolo
Copy link
Contributor

Maven staging often takes longer than the default 5 minutes. Increase to 10.

Currently we are seeing the following error:

Waiting for operation to complete...
....................................................................................................
[WARNING] TIMEOUT after 302.4 s
[ERROR] Rule failure while trying to close staging repository with ID "softwareamazon-7956".
[ERROR] 
[ERROR] Nexus Staging Rules Failure Report
[ERROR] ==================================
[ERROR] 
[ERROR] 
[ERROR] Cleaning up local stage directory after a Rule failure during close of staging repositories: []
[ERROR]  * Deleting context 4714fd1f794.properties
[ERROR] Cleaning up remote stage repositories after a Rule failure during close of staging repositories: []
[ERROR]  * Dropping failed staging repository with ID "softwareamazon-7956" (Rule failure during close of staging repositories: []).

Side note

We already implemented this change years ago in publib, we should really switch over to publib.

See cdklabs/publib#30


By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@iliapolo iliapolo requested a review from a team September 24, 2024 18:10
@mergify mergify bot merged commit cec2d33 into main Sep 24, 2024
7 checks passed
@mergify mergify bot deleted the epolon/increase-maven-staging-timeout branch September 24, 2024 18:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants