@jglick , @oleg-nenashev Using xtrigger-plugin as a guide, I'd suggest that the following should be grouped together as previously owned by Gregory. As such, please could I be added as maintainer on github to:
- FSTrigger Plugin <https://wiki.jenkins.io/display/JENKINS/FSTrigger+Plugin> - https://github.com/jenkinsci/fstrigger-plugin - URLTrigger Plugin <https://wiki.jenkins.io/display/JENKINS/URLTrigger+Plugin> - https://github.com/jenkinsci/urltrigger-plugin (not required, I'm already maintainer) - IvyTrigger Plugin <https://wiki.jenkins.io/display/JENKINS/IvyTrigger+Plugin> - https://github.com/jenkinsci/ivytrigger-plugin - ScriptTrigger Plugin <https://wiki.jenkins.io/display/JENKINS/ScriptTrigger+Plugin> - https://github.com/jenkinsci/scripttrigger-plugin (This looks like something full of security holes and possibly in need of deprecation) - BuildResultTrigger Plugin <https://wiki.jenkins.io/display/JENKINS/BuildResultTrigger+Plugin> (a.k.a JobTrigger) - https://github.com/jenkinsci/buildresult-trigger-plugin - XTrigger-Lib - https://github.com/jenkinsci/xtrigger-lib - EnvInject-Lib - https://github.com/jenkinsci/envinject-lib - XTrigger-Plugin - https://github.com/jenkinsci/xtrigger-plugin I note that EnvInject has since been converted to a plugin - should I include this, or are you happy with the current setup for it? Another point to note - given that the goal for xtrigger-lib is to convert to a plugin, the natural name for it would be xtrigger-plugin. But that's obviously taken as noted above - rather than go off on the wrong track, would 'xtrigger-base-plugin' seem reasonable? Thanks, Tony (GitHub id: TonyNoble , Jenkins id: StealthDJ) On Thu, Jul 11, 2019 at 11:48 PM Tony Noble <tony.no...@gmail.com> wrote: > Pull request submitted for release permissions: > https://github.com/jenkins-infra/repository-permissions-updater/pull/1216 > > Could I also be give access to the github repo for xtrigger-lib, please? > > Repo: https://github.com/jenkinsci/xtrigger-lib > GitHub id: TonyNoble > Jenkins id: stealthdj > > I'll look at what other plugins depend on xtrigger and submit a separate > request for those. Judging by the issues I've discovered with this update > and previous conversations, I'm guessing that envinject may well also need > to be included. > > Thanks, > > Tony > > On Thu, Jul 11, 2019 at 7:00 PM Jesse Glick <jgl...@cloudbees.com> wrote: > >> On Thu, Jul 11, 2019 at 10:27 AM Tony Noble <tony.no...@gmail.com> wrote: >> > any breaking change of the xtrigger plugin would require all dependant >> plugins to be updated and a co-ordinated release organised >> >> Yes…so do not make breaking changes. >> >> > The issue I see there is that (from what I can see) all the dependent >> plugins, or at least a lot of them, were maintained by Gregory and are now >> effectively unmaintained >> >> I would advise anyone taking over as owner of part of this to ask to >> be made owner of all of them. (Does not mean other interested parties >> cannot contribute or even be primarily responsible for substantive >> changes—just means that you have permissions to make changes to the >> whole set of things when you need to.) >> >> -- >> 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 jenkinsci-dev+unsubscr...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr1N9RfJVZt%3Dtf%2BZtgA%3DHcL%2BdcFjjWxFrJjuVoxESqny%2Bg%40mail.gmail.com >> . >> For more options, visit https://groups.google.com/d/optout. >> > -- 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 jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAEWqh9G1Wy0MMMwZCidQ8E_SU9AzXovf1tLdSEL_HJpATKsvhA%40mail.gmail.com.
