Ping @Admins of the JenkinsCI org :-) > On 18 Apr 2018, at 10:05, Luca Milanesio <luca.milane...@gmail.com> wrote: > > Any news on this request? > > I would wait a couple of days more and if there is no movement, I'll have no > choice but forking it :-( > I agree with Daniel, forking would create confusion. > However, having a plugin that extract statistics and is up-to-date with > Jenkins 2.0 and Pipelines is definitely needed. > > Let me know if you guys have other options :-) > > As proposal for the forked plugin name: > "Events Collector"
Thinking aloud, a *brand new* fork could make a lot of sense, because the collection of the events should be de-coupled from the implementation of its transports. The current structure of this plugin, instead, has the transport hardcoded in it, which isn't good at all. I added the support for LOGBack which is good, because allows to de-couple the appenders' transport by just configuring it in the logback.xml. The *brand new* fork could then called: "LOGBack Events Collector" The "out-of-the-box" benefits would be huge on the varieties of transports available for LOGBack: - storage to a DB - ElasticSearch - NATS - Kafka - pure Socket - ... What do you think? Should I just start over? Luca. > > Luca. > > >> On 10 Apr 2018, at 08:00, Daniel Beck <m...@beckweb.net> wrote: >> >> >>> On 10. Apr 2018, at 08:45, Luca Milanesio <luca.milane...@gmail.com> wrote: >>> >>> What is the wait time for getting this escalated and giving the possibility >>> to fix bugs on the plugin? >>> Alternatively, should I just submit a brand-new plugin proposal? (which >>> could cause confusion: people may not know which one is "active") >> >> Two weeks is the typical waiting time after reaching out to maintainers >> directly. >> >> Up to you whether you create a new plugin, but like you point out, "plugin >> overload" has in the past been a source for user confusion and irritation. >> > -- 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/90CED165-C7FD-4E1C-A245-B5B2176639A9%40gmail.com. For more options, visit https://groups.google.com/d/optout.
