Hi, would you mind to rename it during the fork to e.g. JiraIssueCreator-plugin or something like this? IMHO TestResultReporter is little bit confusing - personally I would imagine that such plugin updates existing issues or somethig like this, which is already implemented (though not sure if JiraIssueCreator-plugin is the best choice, any better suggestions are welcome). Thanks Vojta
On Saturday 23 March 2013 09:06:15 Stephan Esch wrote: > Hi! > > I created a plugin that examines the build job for failed unit tests. If * > new* failed tests are detected, it will create an issue for every test case > in Jira. > > It's hosted at github: https://github.com/maplesteve/JiraTestResultReporter > so you can fork from there. > > My github ID is maplesteve > My jenkins-ci.org ID is also maplesteve > > I'll update the pom file etc. according to > to https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins as soon as I > get the hosting confirmation. > > Please don't hesitate to ask, if you any need any further information. > > Thanks & 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
