Hi Oleg and Wolfgang, thanks Wolfgang for your answer. We got Dynatrace already in the Plugin title: "Performance Signature with Dynatrace Plugin". Do we have to update the artifactId, since we use plugin in several environments?
Kind regards, Raphael Am Montag, 23. November 2015 10:38:08 UTC+1 schrieb Wolfgang Gottesheim: > > Hi, > > It looks like I can't post to Google groups from the work email address I > initially used here, sorry about the delay in getting back to you... > > - I'm also fine with replacing the current plugin with the new one, as it > kind of replaces/augments the existing plugin anyway. > - I agree that the "dynatrace" prefix makes sense in any case. > > > Am Sonntag, 27. September 2015 21:43:47 UTC+2 schrieb Oleg Nenashev: >> >> I've added the Dynatrace plugin owner to Cc. It would be great to get his >> feedback before going forward. >> >> Even if we go forward with a new plugin: >> * performance-signature is vague IMHO >> * If the plugin is dynatrace-specific, I would prefer to see "dynatrace" >> in its name >> >> пятница, 25 сентября 2015 г., 10:25:20 UTC+3 пользователь Raphael Pionke >> написал: >>> >>> Any update to this? >>> >>> Kind regards, >>> Raphael >>> >>> Am Dienstag, 22. September 2015 11:09:59 UTC+2 schrieb Raphael Pionke: >>>> >>>> Hi Oleg, >>>> >>>> we know the other Dynatrace plugin and after a long evaluation, we >>>> have decided to developed a new plugin with (good) serious reasons >>>> >>>> >>>> - completely different Workflow (the new plugin consists of several >>>> build-steps and a post-processing step) >>>> - both Plugins can only handle Dynatrace as APM Tool, in future >>>> plugin versions Dynatrace will be replaced by other APM Tools >>>> the original Plugin can only handle Dynatrace as APM Tool, the new >>>> Plugin is designed to be independent from a specific APM-Tool >>>> (although >>>> currently only Dynatrace is supported) >>>> - different approach to gain performance data (the current plugin >>>> uses a xml-report, the new uses Dynatrace Rest API) >>>> - code reuse or integration is not imaginable / requires a hugh >>>> effort >>>> - the most important thing is; the old Dynatrace plugin can only >>>> handle Unit tests, the new plugin can deal with different kinds of >>>> tests >>>> e.g. performance/load test, interfacetest, ui-test … >>>> >>>> I thTo avoid name conflicts the plugin name should be like this: >>>> performance-signature >>>> >>>> Regards, >>>> Raphael >>>> >>>> >>>> Am Mittwoch, 16. September 2015 11:37:20 UTC+2 schrieb Oleg Nenashev: >>>>> >>>>> There is and existing plugin for Dynatrace, which does the similar >>>>> thing. https://wiki.jenkins-ci.org/display/JENKINS/Dynatrace+Plugin >>>>> >>>>> What is the difference between plugins? Would it be possible to merge >>>>> the functionality? >>>>> >>>>> вторник, 15 сентября 2015 г., 15:00:17 UTC+3 пользователь Raphael >>>>> Pionke написал: >>>>>> >>>>>> Hi, >>>>>> >>>>>> this plugin fetches performance values from Dynatrace XML Dashboards >>>>>> during a build and evaluates and compares the result with previous >>>>>> builds >>>>>> and non-functional requirements. This plugin uses user-specified XML >>>>>> Dashboards and PDF detail Reports. Additionally this plugin adds several >>>>>> build steps to trigger the Dynatrace REST interface. >>>>>> >>>>>> Plugin name: performance-signature-dynatrace >>>>>> Github ID: rpionke >>>>>> Repository: https://github.com/T-Systems-MMS/perfsig-jenkins >>>>>> >>>>>> It would be nice to have it hosted on jekins-ci. >>>>>> >>>>>> Thanks in advance, >>>>>> Raphael >>>>>> >>>>>> >>>>>> <https://lh3.googleusercontent.com/-ew4USvsk48A/VfgGgzw295I/AAAAAAAAAXs/PjxzodPRLUM/s1600/performance_signature_plugin.png> >>>>>> >>>>> -- 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/4dcb1967-d92e-42b8-a37e-71152d3971ae%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
