Create a failBuild flag or other type of notification in case of "WARN: Detected empty commit - aborting git push"

[Kankarollo]

Tell us more.

Can we add some failBuild flag of any sort to renovate configuration which would make the status exit 1 of renovate in case of errors like "WARN: Detected empty commit - aborting git push".

The issue that I want to solve is that we found that renovate didn't create PRs for our repository for over a month because of this:

{
    "name": "renovate",
    "hostname": "eb9ec700e6c2",
    "pid": 1,
    "level": 20,
    "logContext": "C88U1kRVAyKz2DVdF4K81",
    "repository": "REDACTED_ORGANIZATION/REDACTED_REPOSITORY",
    "repoProblems": [
        "WARN: Detected empty commit - aborting git push"
    ],
    "msg": "repository problems",
    "time": "2024-11-07T08:55:36.563Z",
    "v": 0
}

We have renovate running on premise in CI pipeline. Below error comes from pip-compile manager after it failed because of conflicts. Didn't send full logs because it's internal repository. If more logs would be helpful for conversation I will send it with some redaction.

...
"message": "Command failed: pip-compile --no-emit-index-url --output-file=requirements.txt requirements.in --upgrade-package=starlette==0.40.0\n  ERROR: Cannot install -r requirements.in (line 1) because these package versions have conflicting dependencies.\nTraceback (most recent call last):...
...
        

I'm thinking how we could solve such issue to give better notification about errors. In my opinion the best option would be to have configuration flag that would allow for failing build in CI pipeline. Other option that I see is to still be able to create a PR which will have artifact error with logs. Maybe to add some dummy file that would allow to create PR.

[rarkins]

Try using logLevelRemap to remap it from warn to error, and you should then get a non-zero exit code (Renovate exits with non-zero if any error or fatal log messages occurred)

[Kankarollo]

Will verify that. Thanks for suggestion.

[Kankarollo]

...and for quick answer.

[Kankarollo]

Verified it and I see in logs anyway that I receive few logs with "level": 40 (ERROR), so from what you are saying I should receive non zero exit status code. Sadly, that's not the case. Is that need additional enabling or maybe it's working differently when you are using pip-compile manager?

More information about how I execute renovate:

My renovate version: 38.142.7
Env variables set:

• RENOVATE_CONFIG_FILE=
• LOG_FORMAT=json
• LOG_LEVEL=debug

[rarkins]

Yes renovate should exit with non zero if there's any errors logged. If that's not the case please create a separate discussion with minimal steps to prove/reproduce

[Kankarollo]

Ok, there is no issue. "level": 40 is WARN in node-bunyan logging. Changed the logging to ERROR with logLevelRemap and indeed it is exiting with status code 1.

Thanks for help with that.

[github-actions[bot]]

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 all

If 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 app

Select me to read instructions

If you use the Mend Renovate app (GitHub):

1. Log in to the Mend Developer Portal
2. Navigate to the correct organization and repository
3. Locate the appropriate log (it may not always be the latest one)
4. Copy/paste the log contents
5. Follow the steps in the formatting your logs section

Finding logs when self-hosting

Select me to read instructions

Read the Renovate docs, troubleshooting, self-hosted to learn how to find the logs.

Insufficient logs

Select me to read instructions

If 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 logs

Select me to read instructions

Please put your logs in a <details> and <summary> element like this:

<details><summary>Select me to see logs</summary>

```
Copy/paste your logs here, between the starting and ending backticks
```

</details>

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