Repository navigation
Feedback wanted: Renovate's monorepo support #41410
Replies: 4 comments 7 replies
|
Our monorepo requires:
I am a (select multiple if appropriate):
Package ecosystems we're using: npm , docker, github-actions Number of branches we manage: 1 Positives of Renovate's monorepo support: Works perfect Length of last Renovate run: 58 s Additional feedback: Thank you very much for your effort |
|
I have basically the same requirements / experience here. Renovate works okay-ish for us, but we run into #40474 with our npm monorepo. Our monorepo requires:
I am a (select multiple if appropriate):
Package ecosystems we're using: npm, docker, github-actions Number of branches we manage: 1 Positives of Renovate's monorepo support:
Negatives of Renovate's monorepo support:
Length of last Renovate run: 1m 18s Thanks a lot. |
|
Our monorepo requires:
I am a:
Package ecosystems we're using: npm (60+ Yarn workspaces), Go (go.work with 60+ modules), PyPI (Poetry), Docker, GitHub Actions Number of branches we manage: 1 Positives of Renovate's monorepo support:
Negatives of Renovate's monorepo support:
Workarounds / config hacks we've found to work really well:
Length of last Renovate run: ~3h+ (last run ended early due to the 422 abort described above; a full successful run would be significantly longer, as individual Go dependency updates affecting many workspace modules can each take 20–30 minutes) |
|
Our monorepo requires:
I am a (select multiple if appropriate):
Package ecosystems we're using: Gradle — 941 dependency entries; Gradle wrapper — 71; custom regex manager — 147. Positives of Renovate's monorepo support: Negatives of Renovate's monorepo support: Lack of other ways to provide dashboards than an issue in the repo, we would love to have one dashboard per project to provide more visibility to the teams. We should probably fix this, but we are running renovate as CLI in Buildkite without storing/persisted cache and we are finding issues with the PR cache in Github, we have over 230K PRs in the mono repo and with the PR creation rate we have, it is not unfrequent that renovate does not retrieve PRs that are just days old, we will work on having a persistent cache and increate the max page limit in the mean time but it seems that the defaults simply does not work and it is not properly documented how to make it work with big monorepos. Workarounds / config hacks we've found to work really well: Length of last Renovate run: 35m (we merged most of the PRs this week and we are at 75 branches) Additional feedback: |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
We (the Renovate maintainers) are seeking community feedback on how Renovate makes updates to monorepos.
We're looking to understand:
Repository finishedlog message at the end of the run)In-scope:
Out-of-scope:
group:monoreposTemplate:
All reactions