Update waves?

[chrisburrell]

Tell us more.

Hi

Perhaps this is already possible but wondering if there might be a way to configure or add a way to configure update waves.

It's a reasonably mainstream scenario to be managing many microservices and instead of deploying updates to all of them in one go, one would want to deploy just 10% on day one, 30% on day two and the rest on day y, etc. and then have a mechanism to pause. In the case of renovate only outside the dependency that might be failing rather than all of them.

It's that something that can be done?

I think one thing I saw was to wait till the update has aged before raising an auto-mergeable PR. And I could use different schedules to hard code finder targets for different services at different rates at different schedules. Is there an easy way of targeting repos by anything other than names?

However, I think aside from being a bit clumsy, I would have to manually add new repos into a particular wave and might end up with lots of failing PRs if the tests fail or worse, issues in production across all services if a particular scenario escapes the testing.

I know some systems assign a number between 1-100 to a file/metadata on creation of the resource and then the eligibility checks for upgrades take that into account by only applying to nodes 1-20, etc. I wonder if that could be sorted as part of onboarding or perhaps there's a better way.

In our case we would apply it to libraries like spring but also our internal framework library which underpins our services.