Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Having a Bugzilla bug update trigger another system
17 views
Skip to first unread message
Andy
Apr 30, 2012, 9:52:33 PM4/30/12
to
We're looking at triggering an external process on our servers when a
Bugzilla bug (a bug that is contained within a given Bugzilla query) is
changed.
Historically, we've had a cron to do this (the cron polls our Bugzilla
3.4.2 instance for any updated bugs on a regular basis), but it would be
great if we could trigger this process only when necessary. I guess it
might be possible to do something through Bugzilla email notifications
(e.g. checking an email inbox for incoming Bugzilla notifications that
meet some criteria), but is there any other / easier way of having
Bugzilla changes notify or trigger some other system?
Bugzilla bug (a bug that is contained within a given Bugzilla query) is
changed.
Historically, we've had a cron to do this (the cron polls our Bugzilla
3.4.2 instance for any updated bugs on a regular basis), but it would be
great if we could trigger this process only when necessary. I guess it
might be possible to do something through Bugzilla email notifications
(e.g. checking an email inbox for incoming Bugzilla notifications that
meet some criteria), but is there any other / easier way of having
Bugzilla changes notify or trigger some other system?
David Marshall
Apr 30, 2012, 10:16:13 PM4/30/12
to devel...@bugzilla.org, dev-apps...@lists.mozilla.org
On 4/30/12 6:52 PM, "Andy" <anfi...@yahoo.com> wrote:
> We're looking at triggering an external process on our servers when a
> Bugzilla bug (a bug that is contained within a given Bugzilla query) is
> changed.
>
We do something like this on our 3.6 instance, using the bug_end_of_create
> We're looking at triggering an external process on our servers when a
> Bugzilla bug (a bug that is contained within a given Bugzilla query) is
> changed.
>
and bug_end_of_update hooks. On 3.4, these hooks appear to be called
bug-end_of_create and bug-end_of_update.
David Marshall
Apr 30, 2012, 10:16:13 PM4/30/12
to devel...@bugzilla.org, dev-apps...@lists.mozilla.org
> We're looking at triggering an external process on our servers when a
> Bugzilla bug (a bug that is contained within a given Bugzilla query) is
> changed.
>
> Bugzilla bug (a bug that is contained within a given Bugzilla query) is
> changed.
>
We do something like this on our 3.6 instance, using the bug_end_of_create
and bug_end_of_update hooks. On 3.4, these hooks appear to be called
bug-end_of_create and bug-end_of_update.
and bug_end_of_update hooks. On 3.4, these hooks appear to be called
bug-end_of_create and bug-end_of_update.
> Historically, we've had a cron to do this (the cron polls our Bugzilla
> 3.4.2 instance for any updated bugs on a regular basis), but it would be
> great if we could trigger this process only when necessary. I guess it
> might be possible to do something through Bugzilla email notifications
> (e.g. checking an email inbox for incoming Bugzilla notifications that
> meet some criteria), but is there any other / easier way of having
> Bugzilla changes notify or trigger some other system?
-
> 3.4.2 instance for any updated bugs on a regular basis), but it would be
> great if we could trigger this process only when necessary. I guess it
> might be possible to do something through Bugzilla email notifications
> (e.g. checking an email inbox for incoming Bugzilla notifications that
> meet some criteria), but is there any other / easier way of having
> Bugzilla changes notify or trigger some other system?
To view or change your list settings, click here:
<http://bugzilla.org/cgi-bin/mj_wwwusr?user=dev-apps...@lists.mozilla.org>
Gervase Markham
May 1, 2012, 5:44:13 AM5/1/12
to Andy
On 01/05/12 02:52, Andy wrote:
> Historically, we've had a cron to do this (the cron polls our Bugzilla
> 3.4.2 instance for any updated bugs on a regular basis), but it would be
> great if we could trigger this process only when necessary. I guess it
> might be possible to do something through Bugzilla email notifications
> (e.g. checking an email inbox for incoming Bugzilla notifications that
> meet some criteria), but is there any other / easier way of having
> Bugzilla changes notify or trigger some other system?
As David said, write a small extension hooking bug_end_of_create and
> Historically, we've had a cron to do this (the cron polls our Bugzilla
> 3.4.2 instance for any updated bugs on a regular basis), but it would be
> great if we could trigger this process only when necessary. I guess it
> might be possible to do something through Bugzilla email notifications
> (e.g. checking an email inbox for incoming Bugzilla notifications that
> meet some criteria), but is there any other / easier way of having
> Bugzilla changes notify or trigger some other system?
bug_end_of_update.
Also, upgrade from 3.4 - it's no longer supported. :-)
Gerv
0 new messages