I'll stick with "JiraTestResultReporter" since this IMO describes best what it actually does. To follow Michael's approach it would then be easy to fork from that and create further plugins for other issue trackers (e.g. "BugzillaTestResultReporter" etc.) or to merge them into a generic one *if* it get's diversified.
Thanks & best regards, Stephan. Am Montag, 25. März 2013 13:25:47 UTC+1 schrieb vjuranek: > > yes, this it true, so it's up to you Stephan how you see the future of > your > plugin:-) Let me know what you prefer and I will fork it accordingly > Thanks > Vojta > > On Monday 25 March 2013 12:17:59 Michael Clarke wrote: > > ... or naming it TestResultReporter would allow extension to support > > reporting test failures to other defect management/issue tracking > systems. > > > > Thanks > > Michael > > > > On 25 Mar 2013, at 11:58, Stephan Esch > > <esch.s...@googlemail.com<javascript:>> > wrote: > > > > Hi! > > > > would you mind to rename it during the fork to e.g. > JiraIssueCreator-plugin > > > > > or > > > something like this? > > > > I agree, that "TestResultReporter" is not the absolutely best name - but > > "JiraIssueCreator" is probably better. It also lays the foundation to > > extend the plugin to report more than failed unit tests. > > > > Best regards, > > Stephan. > -- 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. For more options, visit https://groups.google.com/groups/opt_out.
