No PR's created after switching from app to self-hosted renovate-runner #8205
Answered
by
viceice
timoklok
asked this question in
Request Help
Replies: 1 comment 2 replies
-
|
Beta Was this translation helpful? Give feedback.
2 replies
Answer selected by
viceice
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
No PR's created after switching from app to self-hosted renovate-runner
Hi,
Since the GitLab app went offline, I wanted to switch to a self-hosted version of the Renovate runner. So I followed all the steps from https://gitlab.com/renovate-bot/renovate-runner/-/blob/master/README.md
But I think something is wrong with my config since I don’t get any PR’s (although the log finds all updates for my dependencies and creates an (empty) dependency-dashboard issue). But it’s not clear to me from the log why it isn’t working. I have used the RENOVATE_EXTRA_FLAGS variable to limit Renovate to just one of our repo’s. That repo has it’s own config:
I’m calling the runner via a manual ‘play’ action in my schedules in Gitlab. I’ve added the
schedule: null
config option because I thought maybe the moment I’m calling the runner conflicts with some default schedule option and that’s why no PR’s are made, but that seems to make no difference.Anyone who could help me debug this?
Here’s the full log:
Beta Was this translation helpful? Give feedback.
All reactions