On Thu, Feb 21, 2019 at 4:25 PM Oleg Nenashev wrote: > Hi all, > > Thanks for the responses! If there is no negative feedback, I will proceed > with the implementation next Monday. Whomever wants to add any extra > components to evaluation, please comment in this thread. > > Jesse: Since the primary use case is offering updates to plugin >> repositories, >> I would suggest including at least one example of `*-plugin`. ..... if >> (a) have fairly low installation count (b) are maintained by people >> actively participating in the trial. >> > > maven-hpi-plugin matches the wildcard :P > Speaking seriously, we could try to add some Jenkins plugins to the > experiment if (a) and (b) conditions are met. > If Mark wants to try out his plugins > > The platformlabeler plugin meets conditions (a) and (b). The other two plugins I maintain don't meet condition (a). Definitely enable it on platformlabeler-plugin.
I'm willing to try it on the other two plugins I maintain, but am also fine skipping them if it is not comfortable for the community. I will actively participate in the trial. > Mark: Updates to non-test dependencies are not very helpful for me. When >> dependabot suggests that the git plugin should rely on the latest release >> of some other plugin, it risks placing unnecessary demands on users to >> install newer plugins than are required. I tell dependabot to stop >> offering those dependency updates. It closes the pull requests and stops >> offering updates to that component. >> > > Yes, dependabot can be controlled by GitHubCommentOps or > Configuration-as-Code > <https://dependabot.com/blog/introducing-config-files/>. It may require > maintainers to set up filters, but then it will work like a charm. For > evaluation purposes I would recommend configuration-as-code tho. It may > help us to easily verify the configured filters later. > > That looks great. I'm happy to try the configuration as code route. Mark Waite -- 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/CAO49JtHw_QmYRz%2B%3DQLdJQXmGya-mA0hn%2B6SXov-JwY1t4Qc_jg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
