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

Longer default retry period #12

Closed
szpak opened this issue Jun 12, 2015 · 6 comments
Closed

Longer default retry period #12

szpak opened this issue Jun 12, 2015 · 6 comments
Milestone

Comments

@szpak
Copy link
Member

szpak commented Jun 12, 2015

Find out sensible algorithm.

@adamdubiel
Copy link

How can i check retries count? Should i build my project with -i?

@szpak
Copy link
Member Author

szpak commented Jun 17, 2015

Yes, -i is enough. I will add it to a README file.

@adamdubiel
Copy link

Okay, i will add this to our release plan and get back to you when i have some data.

@szpak
Copy link
Member Author

szpak commented Jun 17, 2015

Great, thanks.

@szpak szpak modified the milestone: 0.5.4 Jun 23, 2015
@adamdubiel
Copy link

Getting back to this issue, i have some data from our new hermes release:

:closeRepository (Thread[Daemon worker,5,main]) started.
build   07-Aug-2015 11:27:38    :closeRepository
build   07-Aug-2015 11:27:38    Executing task ':closeRepository' (up-to-date check took 0.0 secs) due to:
build   07-Aug-2015 11:27:38      Task has not declared any outputs.
build   07-Aug-2015 11:27:39    Getting staging profile for package group pl.allegro
build   07-Aug-2015 11:27:42    Getting open repository for staging profile 19d6feb4b1fb3
build   07-Aug-2015 11:27:42    Closing repository plallegro-1075 with staging profile 19d6feb4b1fb3
build   07-Aug-2015 11:27:43    POST response data: null
build   07-Aug-2015 11:27:43    Repository plallegro-1075 with staging profile 19d6feb4b1fb3 has been closed
build   07-Aug-2015 11:27:43    :closeRepository (Thread[Daemon worker,5,main]) completed. Took 4.802 secs.
build   07-Aug-2015 11:27:43    :promoteRepository (Thread[Daemon worker,5,main]) started.
build   07-Aug-2015 11:27:43    :promoteRepository
build   07-Aug-2015 11:27:43    Executing task ':promoteRepository' (up-to-date check took 0.0 secs) due to:
build   07-Aug-2015 11:27:43      Task has not declared any outputs.
build   07-Aug-2015 11:27:43    Using configured staging profile id: 19d6feb4b1fb3
build   07-Aug-2015 11:27:43    Getting closed repository for staging profile 19d6feb4b1fb3
build   07-Aug-2015 11:27:44    Attempt 1/16 failed. IllegalArgumentException was thrown with message 'Unexpected state of reveived repository. Received open, expected closed'. Waiting 5000 ms before next retry.
build   07-Aug-2015 11:27:49    Getting closed repository for staging profile 19d6feb4b1fb3
build   07-Aug-2015 11:27:50    Promoting repository plallegro-1075 with staging profile 19d6feb4b1fb3
build   07-Aug-2015 11:27:51    POST response data: null
build   07-Aug-2015 11:27:51    Repository plallegro-1075 with staging profile 19d6feb4b1fb3 has been promotted
build   07-Aug-2015 11:27:51    :promoteRepository (Thread[Daemon worker,5,main]) completed. Took 7.521 secs.

@szpak
Copy link
Member Author

szpak commented Mar 27, 2017

I increased default retry count to 20 and delay between retries to 2000 - ~40 seconds + request/response time in 0.7.0. Should be enough in most cases. Feel free to open it if the new default values are still too low and dedicated algorithm for multimodule projects is really needed.

@szpak szpak changed the title Retry timeout should be longer for multimodule projects Longer default retry period Mar 27, 2017
@szpak szpak closed this as completed Mar 27, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants