I think you will find that creating issues automatically from Jenkins will flood your issue tracker with reports and will create organizational overhead managing those reports. Even if you only run your JMeter tests once a day, do you really want an issue submitted per failure per day?
Wouldn't it be better to first try e-mail messages that inform someone about the failure, then they can decide if it is a long-lived failure and might be worth creating an issue? Mark Waite On Mon, Oct 14, 2013 at 10:20 AM, 1042907P <pushparaj...@gmail.com> wrote: > We are using performance plugin for parsing Jmeter test cases and showing > HTML reports.Would like to create JIRA issue upon test case failures. > I have tried JIRA plugin ,but it does not even trigger the post build > action. > Please advise > > > > -- > View this message in context: > http://jenkins-ci.361315.n4.nabble.com/Create-JIRA-issue-on-Jmeter-test-fail-tp4678879.html > Sent from the Jenkins users mailing list archive at Nabble.com. > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
