Support Maven pom with dependencies as input to the tool

[MindaugasLaganeckas]

We would like to propose to support Maven pom file as an input to the plugin manager tool.
E.g.

<dependency>
    <groupId>org.jenkins-ci.plugins</groupId>
    <artifactId>git</artifactId>
    <version>4.4.1</version>
</dependency>

This way we can use dependabot in our repository to check for updates and create PRs, if an update is available. At the moment keeping an eye on the updates requires too much of our time, the same can be said regarding the equivalent implementation of the dependabot using the plugin manager tool.

We love reusing/contributing to existing tools.

What do you think about it? Have you tried anything similar already? Have we missed an important detail, that can block the implementation of this feature?

[oleg-nenashev]

There is https://issues.jenkins-ci.org/browse/JENKINS-58217 for it, but it has not been moved to GitHub issues yet

[timja]

@MindaugasLaganeckas we use https://docs.renovatebot.com/modules/manager/jenkins/ it works perfectly (although only txt file support no yaml atm)

[MindaugasLaganeckas]

@oleg-nenashev & @timja : thank you for such quick response. I will have a look and get back to you. 😄

[oleg-nenashev]

we use https://docs.renovatebot.com/modules/manager/jenkins/ it works perfectly (although only txt file support no yaml atm)

How about Maven upper bounds checks? I doubt Renovate can unravel the Jenkins plugin dependency requirements. But yes, it is a good solution for simple cases

[MindaugasLaganeckas]

@timja : thank you for the recommendation. It is still unclear a bit if renovatebot is completely free of charge also for the private repositories. If you have this information, please, share with me :)
I will close this issue now.

[oleg-nenashev]

I will restore it as feature request