feat(onboarding): skip processing onboarding branch

[RahulGautamSingh]

Changes

• added new variable onboardingCacheValid to the OnboardingState class which is computed at the beginning and is used to determine if the onboardingCache is valid
• added two new fields to the OnboardingBranchCache : configFileName and configFileParsed
• If onboardingCache is valid we reuse this stored info to prevent cloning to find the renovate config file name and its content
  Else onboarding branch is processed and the configFileName and configFileParsed are cached to be used on next run

Context

The GitHub app has something like 50k onboarding repos. So we need some optimizations to reduce the amount of time spent in processing them.
I think if we skip work if main/onboarding branch SHAs are untouched then it’s quick enough
Slack Message @rarkins

Documentation (please check one with an [x])

• I have updated the documentation, or
• No documentation update is required

How I've tested my work (please select one)

I have verified these changes via:

• Code inspection only, or
• Newly added/modified unit tests, or
• No unit tests but ran on a real repository, or
• Both unit tests + ran on a real repository

[ChristianCiach]

Does this help (or make things more complicated) regarding the optimization I've proposed here?

• Perform an API call to check if Renovate is enabled, rather than cloning the repo #18811 (comment)

My use-case consists of tons of repos that do not contain a renovate.json at all. Even though renovate is configured with onboarding: false, all the repos are cloned on every run. My idea is to use the onboarding-cache to skip repos when onboarding: false and we already know that the current branch revision does not contain a renovate.json.

[RahulGautamSingh]

Does this help (or make things more complicated) regarding the optimization I've proposed here?

• Perform an API call to check if Renovate is enabled, rather than cloning the repo #18811 (comment)

My use-case consists of tons of repos that do not contain a renovate.json at all. Even though renovate is configured with onboarding: false, all the repos are cloned on every run. My idea is to use the onboarding-cache to skip repos when onboarding: false and we already know that the current branch revision does not contain a renovate.json.

This PR won't affect your use case since this logic only comes in effect once we know that repoIsOnboarded=false.

[viceice]

otherwise LGTM

[viceice]

otherwise LGTM

[rarkins]

Coverage problem in workers-1 shard

[viceice]

maybe admin merge the lcov change and clear the codecov data

[rarkins]

Needs coverage

[renovate-release]

🎉 This PR is included in version 35.139.0 🎉

The release is available on:

• GitHub release
• 35.139.0

Your semantic-release bot 📦🚀