renovatebot/renovate

Delay between repository scans

Open

#20853 opened on Mar 10, 2023

View on GitHub
 (3 comments) (4 reactions) (0 assignees)TypeScript (14,066 stars) (1,916 forks)batch import
help wantedpriority-4-low

Description

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

Contributor guide

Tech stack
typescriptnodejs
Domain
toolingdeveloper experience
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Familiarity with Renovate self hosted configUnderstanding of repository scanning workflow
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Investigate how Renovate currently schedules repository scans, particularly in self hosted mode. Look at the configuration options related to concurrency and scheduling (e.g., 'onboardingConfig' or 'repositories'). Check if there is an existing delay mechanism or rate limiting. Review the repository scanning logic in the codebase, likely under `lib/workers/repository/` or similar. Consider whether a simple configurable delay between scans could be added, and discuss potential implementation approaches in the issue comments.