search

renovatebot / config-help

Please use the Discussions feature of https://github.com/renovatebot/renovate instead
https://github.com/renovatebot/renovate/discussions
MIT License
27 stars 16 forks source link

Organisation wide configuration and schedule changes #964

Closed msimperi closed 4 years ago

msimperi commented 4 years ago

Which Renovate are you using?

WhiteSource Renovate App

Which platform are you using?

GitHub.com

Have you checked the logs? Don't forget to include them if relevant

Repository X using organisation wide configuration, last time executed. image

Organisation wide configuration repository has been updated and executed. image

What would you like to do?

I added first default configuration value that run dependency updates "early mondey". With this I configured repository X and it started to wait "monday morning". Now I changed organisation wide schedule to be "weekdays" and before that no preset scehdule.

I'm not able to see repository X executed even the main configuration has changed few times. Does the organisation wide configuration change trigger also repository X runs? It seems now that it does not.

viceice commented 4 years ago

Look like caching is defering runs, try to use the trigger run checkbox from dependencyDashboard, that should reevaluate all configs

msimperi commented 4 years ago

Sadly I didn't have that one already enable for repository X. I enabled it now in base configuration, but it still does not seem to trigger repository x run...

rarkins commented 4 years ago

Repos in onboarding stage aren't checked hourly

msimperi commented 4 years ago

The repository was not anymore in on-boarding stage. I have accepted the PR already, but it seems that the main-config change on schedule do not activate automatically in repository x using that main config.

msimperi commented 4 years ago

Here are techinical job ids: 254966587 and 255393657.

viceice commented 4 years ago

can you paste the relevant logs here, as we can't easily view your logs without being a member of your repo

rarkins commented 4 years ago

And FYI there is no chain reaction where commits to a base config in repo X are detected and trigger all downstream repos to run

msimperi commented 4 years ago

I made a small change to target repository and was able to trigger re-run for it. Now it seems to work correctly. I also created dashboard issue to trigger runs again if needed manually.

Thanks @viceice and @rarkins for the help!