+1 for integrating changes into the existing plugin. Patrik's implementation is quite different, but seems there's no technical showstoppers. The original plugin's backend can be reworked and release as performance-2.x
вторник, 30 декабря 2014 г., 15:38:03 UTC+3 пользователь evernat написал: > > It would be great if the existing plugin could be improved for those > issues, via github pull requests. > If it can not, I would like to here the maintainer of that plugin and / or > other devs about hosting another plugin. > > Please be patient, > Emeric > > > Le lundi 29 décembre 2014 20:15:20 UTC+1, Patrik Persson a écrit : >> >> Yes I know that plugin exists. I have used it in previous projects and >> suffered from its shortcomings. See >> https://issues.jenkins-ci.org/browse/JENKINS-20848 and >> https://issues.jenkins-ci.org/browse/JENKINS-22385 for more info on the >> issues I faced. As you can see, one of the tickets is more than 12 months >> old. >> >> I decided to write my own plugin to solve my problem and figured I would >> share it with the community. I understand that having two plugins with the >> same name / purpose isn't ideal and that the current plugin has been >> adopted and has more functionality. If it was fixed that would be great. >> >> If you think having two plugins that competes with each other is bad then >> I guess you have to decide which on you wan't to push. If nothing else I >> will host my plugin on my site and hope that a search engine picks it up. >> Maybe someone else can use it to do long running JMeter testing without >> crashing Jenkins. >> >> Let me know if you wan't to host my plugin, I will be glad to share it! >> >> Regards, >> >> - Patrik >> >> 2014-12-26 19:39 GMT+01:00 evernat <[email protected]>: >> >>> In fact, the name "performance-plugin" is generic enough that a plugin >>> already exists with that name: >>> https://wiki.jenkins-ci.org/display/JENKINS/Performance+Plugin >>> And this one is doing performance report based on JMeter results (seems >>> like yours) and is maintained. >>> It's not great to have two plugins with the same description. So, would >>> it be possible to enhance and add your features in the existing plugin, for >>> example with github pull requests? >>> A discussion may happen with the maintainer of the existing plugin. >>> >>> Emeric >>> >>> Le vendredi 26 décembre 2014 16:18:44 UTC+1, Patrik Persson a écrit : >>>> >>>> Great idea! >>>> >>>> I suggest calling it jmeter-report-plugin since that's what it handles. >>>> >>>> On Friday, December 26, 2014 11:43:55 AM UTC+1, Kanstantsin Shautsou >>>> wrote: >>>>> >>>>> This is very generic name for plugin. As i understand it tied to >>>>> jmeter, better name it like jmeter-results-plugin or >>>>> jmeter-something-plugin >>>>> >>>>> On Thursday, December 25, 2014 11:00:11 PM UTC+3, Patrik Persson wrote: >>>>>> >>>>>> Requesting access to Jenkins CI plugin repository >>>>>> >>>>>> Plugin name: Performance Report >>>>>> Github Id: patpe >>>>>> Github repo to fork: https://github.com/patpe/performance-plugin.git >>>>>> >>>>>> Regards, >>>>>> >>>>>> - Patrik >>>>>> >>>>> -- >>> You received this message because you are subscribed to a topic in the >>> Google Groups "Jenkins Developers" group. >>> To unsubscribe from this topic, visit >>> https://groups.google.com/d/topic/jenkinsci-dev/mM9ouME4T3Q/unsubscribe. >>> To unsubscribe from this group and all its topics, send an email to >>> [email protected]. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/jenkinsci-dev/ccf935d6-640c-4002-ba4b-25dde772d380%40googlegroups.com >>> >>> <https://groups.google.com/d/msgid/jenkinsci-dev/ccf935d6-640c-4002-ba4b-25dde772d380%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >>> 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/0cb1b4c7-8796-4694-a2fc-795c00ba6597%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
