Renovate doen't fail if repository can not be reached. #29085
Closed
steffakasid
started this conversation in
Suggest an Idea
Replies: 4 comments 11 replies
-
|
Please provide the full debug logs |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Hi there, This issue or discussion is missing some logs, making it difficult or impossible to help you. Depending on which situation applies follow one, some or all of these instructions. No logs at allIf you haven't posted any log yet, we need you to find and copy/paste the log into the issue template. Finding logs on hosted appSelect me to read instructionsIf you use the Mend Renovate app (GitHub):
Finding logs when self-hostingSelect me to read instructionsRead the Renovate docs, troubleshooting, self-hosted to learn how to find the logs. Insufficient logsSelect me to read instructionsIf you already gave us a log, and the Renovate team said it's not enough, then follow the instructions from the No logs at all section. Formatting your logsSelect me to read instructionsPlease put your logs in a If you feel the logs are too large to paste here, please use a service like GitHub Gist and paste the link here. Good luck, The Renovate team |
Beta Was this translation helpful? Give feedback.
0 replies
-
As the log contains a lot of information. I can't publish it completely so here is an excerpt. Were you can see the issue... |
Beta Was this translation helpful? Give feedback.
7 replies
-
|
There are two possibilities:
|
Beta Was this translation helpful? Give feedback.
-
|
I think the 2nd idea would be the best. So we can still receive PRs for everything not failing and get the information that something went wrong and needs our attention. |
Beta Was this translation helpful? Give feedback.
-
|
Actually I just noticed that you already have (1) today: If you want a non-zero exit code then you could use logLevelRemap to change |
Beta Was this translation helpful? Give feedback.
-
|
Do you have any documentation available for this? |
Beta Was this translation helpful? Give feedback.
-
|
https://docs.renovatebot.com/configuration-options/#loglevelremap I'll try this out and close here. |
Beta Was this translation helpful? Give feedback.
-
|
Here is another log with debugging enabled: |
Beta Was this translation helpful? Give feedback.
4 replies
-
|
This log doesn't include the error from the earlier log |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
Interesting this is a DEBUG message. Unfortunately I just searched for |
Beta Was this translation helpful? Give feedback.
-
|
If you fail Renovate for any artifact update error then you're going to have a bad time. You are better to let developers handle those - you will get a PR comment any time they happen. |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Tell us more.
Hi,
we just had an issue that we saw the following error in the renovate logs:
"message": "write EPROTO 0008F977237F0000:error:0A00010B:SSL routines:ssl3_get_record:wrong version number:../deps/openssl/openssl/ssl/record/ssl3_record.c:355:\n",unfortunately this error didn't fail renovate it looked like it was finishing correctly. In our case this error just occured because we tried to access a remote repo which wasn't proxy whitelisted. After doing so the error was gone.I would like to suggest to fail in those situations, so that users are aware that something needs to be done. Also the error message is very cryptic.
Regards
Steffnen
Beta Was this translation helpful? Give feedback.
All reactions