How to Automate Dependency Updates with the Renovate@Roche Bot
summary
Roche runs a self-hosted Renovate Docker image that scans project lists, creates onboarding merge requests, and updates dependencies via GitLab CI scheduled every 2 hours. Configuration lives in renovate.json and server-side host rules; a GitHub token fetches release notes. The instance parallelizes work with 12 jobs in parallel, enforces assignees to prevent ignored MRs, and can auto-merge when CI is green. It succeeds at bulk maintenance but requires admin tuning (host credentials, PR limits, ignored versions) to avoid failing updates like a Python 3.12 break.
AI-written summary · about
chapters (12)
- 0:00Automating dependency updates
- 3:54What is Renovate
- 7:07Renovate with Docker & GitLab
- 11:20Self-hosted GitLab config
- 15:54First Renovate merge request
- 21:38Custom config per project
- 26:18Merge requests & auto-merging
- 31:56Failed updates & ignored versions
- 34:00Renovate community tips
- 37:11Key takeaways
- 42:33Final demo & closing
- 42:53Q&A
related talks
45mHow to Automate Dependency Updates with the Renovate@Roche Bot
33mUsing Renovate to keep your version dependencies updated
33mAutomated update management with
31mRenovate/Dependabot: How to Take Back Control of Dependency Updates
16mRenovate to the Rescue
41mRenovate/Dependabot: How to Reclaim Control Over Dependency Updates
25mRenovate, or how to keep your project up to date!
33mKeep your dependencies in check
