Closed ext closed 5 years ago
rarkins
commented
5 years ago We have logic to detect "stale" repos with no commits for months, and then take them off the regular hourly/daily schedules. In this case most of the ones in this org fall into that:
What's a pity is that your merging of the onboarding MR itself hasn't achieved the result of removing that status.
I have manually removed the status of each repo and they should hopefully be picked up within the next hour or two.
ext
commented
5 years ago Thanks for the quick response! That makes sense, perhaps it could indicate somewhere (dashboard?) to the user as well that it is considered stale?
rarkins
commented
5 years ago Yes, that's a good idea. We have a lot of plans to make that dashboard more informative..
ext
commented
5 years ago Confirmed working for all repos, thanks again! Closing this issue now.
noraj
commented
4 years ago @rarkins Same issue here. I installed the renovate app on my gitlab.com repos but I'm not receiving any onboarding (MR, by the way PR are for github see Comparing confusing terms in GitHub, Bitbucket, and GitLab (2017))
And the dashboard remains empty, no error or stale satus display:
The dev user and the webhook are both present.
What Renovate type are you using? Renovate GitLab App
Describe the bug RenovateBot doesn't seem to run anything since initial onboarding PR, trying to reconfigure doesn't help either.
Installing/uninstalling adds/removes the @renovate-bot user as developer but not webhook is added. Using devtool on dashboard shows requests to
https://v1.renovateapi.com/gitlab/repos/.../webhooksgiving 404.Did you see anything helpful in debug logs? Dashboard lists project but no jobs, the initial onboarding job disappeared.
Expected behavior Renovatebot should start running jobs.
Additional context
I first tried renovate on a single repo in organization. Worked fine.
When trying to add it to others the first additional one installed properly, the rest got onboarding PRs but nothing after merging it.