That seems like a good case to review the video "Dependabot for Jenkins plugin development" <https://www.youtube.com/watch?v=RXIJpjYlECQ> . If you're working on a Jenkins plugin, it offers good suggestions. Many Jenkins repositories are using dependabot now.
On Thu, Jul 8, 2021 at 4:37 AM Ullrich Hafner <[email protected]> wrote: > Are you talking about dependencies in general? Then this is the wrong > mailing list. > > If you are interested in how to update plugin dependencies. We all use > dependabot [1] to keep them up to date. > > [1] > https://github.blog/2020-06-01-keep-all-your-packages-up-to-date-with-dependabot/ > > > Am 08.07.2021 um 11:02 schrieb mr.Gray <[email protected]>: > > Hi, > > I looking for best practice to keep all the dependencies and parent of > maven project to up to date. And if there are new version available only > then update the pom version and push to git (which will launch the build of > app). I'm ok with running this manually or periodically. > > I'm about to use the "mvn versions:display-dependency-updates" and reading > the output if any new updates to desired dependencies (it would be nice to > include by groupid) and mvn versions:update-parent to check the parent. > > But the reading the output on pipeline feels a bit "hackish", also I have > several of these apps, which also makes me feel should I use something else. > > Simplified pom example: > App5 > -- parent: app1, version1 <--- update pom version if new available > --dependency1: app2, version1 <--- update pom version if new available > --dependency2: app3, version1 <--- update pom version if new available > --dependency3: app4, version1 <--- do not update > > Any help would be appreciated, thank you in advance! > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/6ce50a71-2627-44f1-b90b-56ff905edb32n%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-dev/6ce50a71-2627-44f1-b90b-56ff905edb32n%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/4FC829FA-FF6C-42AD-8C05-E1C623F08AAE%40gmail.com > <https://groups.google.com/d/msgid/jenkinsci-dev/4FC829FA-FF6C-42AD-8C05-E1C623F08AAE%40gmail.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtFpVM8q%3DF9jKLZ4y%2Biv20q-CGo97srx9S-VmuX%2BtVrx2w%40mail.gmail.com.
