gradle replacement dependency causes branch update to fail with status 0 #34685
Unanswered
Mousterian
asked this question in
Request Help
Replies: 1 comment 1 reply
-
Yes, I think Renovate should ignore replacement MRs for gradle. Adding a |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
How are you running Renovate?
Self-hosted Renovate
If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.
Gitlab
Please tell us more about your question or problem
Hi,
I have a problem related to this topic and I'm trying to work out if it is a bug:
I have a self hosted setup (running renovate 39.182.3), in my target repository there is a gradle build with a dependency that has replacement available, e.g. org.hibernate:hibernate-validator
When renovate runs I get a warning:
WARN: gradle manager does not support replacement updates yet
which is fair enough, the feature is not there yet.
Then I get an error logged as a warning about not being able to update the branch:
WARN: Error updating branch: update failure (repository=<***redacted***>, branch=renovate-group-all)
There are other dependencies available to upgrade but renovate-group-all is not updated, and renovate exits with status 0 so the pipeline succeeds.
If I suppress the replacement dependency with a packageRule, e.g.
then renovate ignores the suppressed package, and manages to update renovate-group-all with the other eligible dependencies.
So, something seems wrong, I think either renovate should ignore replacement MRs for gradle until they are supported, or it should return an error status so I know I need to suppress those packages. The combination of the failure and no error status meant this was hard to spot and resolve.
Thanks!
Logs (if relevant)
Logs
Beta Was this translation helpful? Give feedback.
All reactions