Hi Daniel,

Automatically filing to bug tracker is working when developer commits code
to SCM when there is test case failure.

But *My query is:*

1) If there is a closed issue with same test case failure in the next
Hudson build. It should reopen the issue in the Bug Tracker (Bugzilla or
Mantis).

2)And if the issue is already open, another ticket shouldn't be filed
instead it should link to the existing issue Id.

BR,
Chethan


On Fri, Sep 13, 2013 at 1:18 PM, Daniel Beck <[email protected]> wrote:

> This doesn't seem to be about issues in Hudson and Jenkins to be filed in
> both projects' bug trackers, but about a Hudson/Jenkins plugin (?) that
> automatically files issues in Chethan's organization's bug tracker when a
> build breaks or tests fail.
>
> On 12.09.2013, at 08:40, Baptiste Mathus <[email protected]> wrote:
>
> > Hi, Jenkins is actually not affiliated to Hudson. Even less today I'd
> say. So if you want to have a fix for both projects, you'll have to file it
> in both bug trackers.
> >
> > Now if a bug you're encountering is closed, there's many possibilities.
> Is it a duplicate? Was it closed in a recent version and you're using an
> older one?...
> >
> > If none of the above you could generally reopen it.
> > If in doubt, let's be a bit more specific here with your actual issue.
> > Cheers
> >
> > Le 11 sept. 2013 12:34, "Chethan B D" <[email protected]> a
> écrit :
> > Hi Jenkins,
> >
> > How can I avoid multiple ticket filing to Bug Tracker from Jenkins /
> Hudson for same test case failure or same exception in the next build if it
> is not resolved?
> > If there is closed issue with same test case failure. It should reopen
> the issue in the Bug Tracker (Bugzilla or Mantis).
> > And if the issue is already open, no action should be taken. that is
> another ticket shouldn't be filed.
> >
> > Anybody please help me out in doing this. How can I update the relevant
> issue in this scenario.
> > Is there any plugin which does this.
> >
> > BR,
> > Chethan
> >
> > --
> > 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.
> >
> > --
> > 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.
>
> --
> 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/FwQHkmX7kQ8/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> [email protected].
> For more options, visit https://groups.google.com/groups/opt_out.
>

-- 
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.

Reply via email to