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

Re-boarding not working #642

Closed agusalex closed 4 years ago

agusalex commented 4 years ago

What Renovate type are you using? Renovate on GitHub, self-hosted

Describe the bug We have many repos that were already onboarded and their pull request closed. As per documentation, I did everything that was required in the "Nuke Everything and re-board" section to no avail since then several days have passed and the bot hasn't shown up.

Did you see anything helpful in debug logs? I cannot access the logs as it is not self-hosted and I'm not the repo owner.

To Reproduce

The repo is private and owned by my organization. The bot had created a "Configure Renovate" pull request before. I followed the documentation but to no avail. Here are the steps that were followed: image

Additional context

rarkins commented 4 years ago

Try adding a renovate.json file manually to one. Pretty hard to tell what’s going on without logs. For all you know the bot may have been uninstalled from those repos

agusalex commented 4 years ago

Did that and still nothing, we got access to the logs, its a gradle project: "message": "Command failed: ./gradlew --init-script renovate-plugin.gradle renovate\n\nFAILURE: Build failed with an exception.\n\n* What went wrong:\nCould not determine java version from '11.0.4'.\n\n* Try:\nRun with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.\n"

rarkins commented 4 years ago

Looks like it doesn't have anything to do with re-boarding and instead is a gradle issue.

I'm not a gradle user but found plenty of results when Googling it. e.g. some answers said JDK 11 wasn't supported until Gradle 5, etc.

If you think it's a Renovate problem, we will probably need a reproduction repo to be able to fix it.

stale[bot] commented 4 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed soon if no further activity occurs.