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.

Sign up for GitHub

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

Jump to bottom

Delay between repository scans #20853

Open
hoerup opened this issue Mar 10, 2023 · 2 comments
Open

Delay between repository scans #20853

hoerup opened this issue Mar 10, 2023 · 2 comments
Labels
good first issue Suitable for new contributors help wanted Help is needed or welcomed on this issue priority-4-low Low priority, unlikely to be done unless it becomes important to more people type:feature Feature (new functionality)

Comments

@hoerup
Copy link

hoerup commented Mar 10, 2023

What would you like Renovate to be able to do?

When using renovate to scan our 100+ onprem microservice repos it puts a load on git server and repo servers, and when there are many updates it also adds quite a queue into the CI system

So i would like for a selfhosted renovate to be able to add a small delay between the repositories and spread the load on before-mentioned systems a bit

If you have any ideas on how this should be implemented, please tell us here.

.

Is this a feature you are interested in implementing yourself?

No
@hoerup hoerup added priority-5-triage status:requirements Full requirements are not yet known, so implementation should not be started type:feature Feature (new functionality) labels Mar 10, 2023
@rarkins rarkins added help wanted Help is needed or welcomed on this issue good first issue Suitable for new contributors priority-4-low Low priority, unlikely to be done unless it becomes important to more people and removed priority-5-triage labels Mar 10, 2023
@HonkingGoose
Copy link
Collaborator

I'm going to assume this is status:ready, because it's labeled a good first issue and help wanted.

@HonkingGoose HonkingGoose added status:ready and removed status:requirements Full requirements are not yet known, so implementation should not be started labels Mar 13, 2023
@jakubrak
Copy link

jakubrak commented Mar 19, 2023 •
edited
Loading

Are you using one Renovate instance? Perhaps subdividing repositories into multiple Renovate instances could solve the problem. See this discussion: #13172
You can also limit the number of concurrent branches or pull requests per repository in Renovate config.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
good first issue Suitable for new contributors help wanted Help is needed or welcomed on this issue priority-4-low Low priority, unlikely to be done unless it becomes important to more people type:feature Feature (new functionality)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@hoerup @rarkins @jakubrak @HonkingGoose