From anfisher at yahoo.com  Tue May  1 01:52:33 2012
From: anfisher at yahoo.com (Andy)
Date: Mon, 30 Apr 2012 18:52:33 -0700
Subject: Having a Bugzilla bug update trigger another system
Message-ID: <EvadneGM3-R43ALSnZ2dnUVZ_uCdnZ2d@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.

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?
_______________________________________________
dev-apps-bugzilla mailing list
dev-apps-bugzilla at lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-apps-bugzilla


From dmarshal at yahoo-inc.com  Tue May  1 02:16:13 2012
From: dmarshal at yahoo-inc.com (David Marshall)
Date: Mon, 30 Apr 2012 19:16:13 -0700
Subject: Having a Bugzilla bug update trigger another system
In-Reply-To: <EvadneGM3-R43ALSnZ2dnUVZ_uCdnZ2d@mozilla.org>
Message-ID: <CBC4957D.46D44%dmarshal@yahoo-inc.com>

On 4/30/12 6:52 PM, "Andy" <anfisher at 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
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?



From gerv at mozilla.org  Tue May  1 09:44:13 2012
From: gerv at mozilla.org (Gervase Markham)
Date: Tue, 01 May 2012 10:44:13 +0100
Subject: Having a Bugzilla bug update trigger another system
In-Reply-To: <EvadneGM3-R43ALSnZ2dnUVZ_uCdnZ2d@mozilla.org>
References: <EvadneGM3-R43ALSnZ2dnUVZ_uCdnZ2d@mozilla.org>
Message-ID: <4F9FB06D.20905@mozilla.org>

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

Also, upgrade from 3.4 - it's no longer supported. :-)

Gerv
_______________________________________________
dev-apps-bugzilla mailing list
dev-apps-bugzilla at lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-apps-bugzilla


From mkanat at bugzilla.org  Mon May  7 22:12:45 2012
From: mkanat at bugzilla.org (Max Kanat-Alexander)
Date: Mon, 07 May 2012 15:12:45 -0700
Subject: Extension architecture help required
In-Reply-To: <4F9DF889.8030706@mozilla.com>
References: <E5mdnRjDjKOE9wfSnZ2dnUVZ_oadnZ2d@mozilla.org> <4F9DF889.8030706@mozilla.com>
Message-ID: <4FA848DD.50505@bugzilla.org>

	Yeah, what Byron says sounds good. Also, another option would be to add 
a hook to Bugzilla::DB::bz_commit_transaction. You could store things in 
$self in the extension during bug_end_of_update and trigger them when 
the transaction was committed. $self in an extension is an object that's 
re-created for every page call, so you're fairly safe there.

	-Max

On 04/29/2012 07:27 PM, Byron Jones wrote:
> hey gerv,
>
> Gervase Markham wrote:
>> In my Sync extension:
>> http://bzr.mozilla.org/bugzilla/extensions/sync/
>> I am using the bug_end_of_update hook to do syncing once a bug is
>> updated.
> i have an extension which is designed to push updates to other systems
> which currently poll bugzilla for updates (pulse, elastic search caches,
> metrics, etc).
> https://github.com/globau/bugzilla-push
> it's extremely close to completion, and is a q2 goal.
>
> i deal with the issue you've encountered by performing serialisation of
> the bug at the time the update is made, in my case to JSON. these are
> inserted into a custom table which a custom daemon polls and sends. i
> don't use the jobqueue system because that doesn't guarantee the order
> of the messages, which is important when you're sending update messages
> (especially when a remote system is down).
>
> since i already have a working system for sending bug updates which
> deals correctly with ordering of the updates, as well as queuing
> messages when the remote system is down, another option would be for the
> update-pushing part of your extension to utilise my bugzilla-push
> extension and be dropped in as another connector. see
> https://github.com/globau/bugzilla-push/tree/master/Push/lib/Connector
>
>
>
> -byron
> --
> byron - irc:glob - bugzilla.mozilla.org team -
>


-- 
Max Kanat-Alexander
Chief Architect, Community Lead, and Release Manager
Bugzilla Project
http://www.bugzilla.org/


From gerv at mozilla.org  Tue May  8 11:39:13 2012
From: gerv at mozilla.org (Gervase Markham)
Date: Tue, 08 May 2012 12:39:13 +0100
Subject: Extension architecture help required
In-Reply-To: <mailman.26078.1336428818.31724.dev-apps-bugzilla@lists.mozilla.org>
References: <E5mdnRjDjKOE9wfSnZ2dnUVZ_oadnZ2d@mozilla.org>
	<4F9DF889.8030706@mozilla.com>
	<mailman.26078.1336428818.31724.dev-apps-bugzilla@lists.mozilla.org>
Message-ID: <QpadnTl3UKp8mDTSnZ2dnUVZ_vmdnZ2d@mozilla.org>

On 07/05/12 23:12, Max Kanat-Alexander wrote:
>     Yeah, what Byron says sounds good. Also, another option would be to
> add a hook to Bugzilla::DB::bz_commit_transaction. You could store
> things in $self in the extension during bug_end_of_update and trigger
> them when the transaction was committed. $self in an extension is an
> object that's re-created for every page call, so you're fairly safe there.

In the end, I just checked for a timestamp mismatch in the job itself
and called $job->declined() if one occurred. That reschedules it after 5
minutes.

Gerv

_______________________________________________
dev-apps-bugzilla mailing list
dev-apps-bugzilla at lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-apps-bugzilla


From joshi_sunil at in.com  Wed May  9 15:11:12 2012
From: joshi_sunil at in.com (Sunil Joshi Joshi)
Date: Wed, 09 May 2012 20:41:12 +0530
Subject: Self-Introduction: Sunil Joshi
Message-ID: <1336576272.b05851605ad0a7613af514cd321a63e3@mail.in.com>

Hi All,Sunil JoshijoshisunilNew Delhi, IndiaSoftware ProfessionalSoftware OrganizationDevelopment and Test AutomationHistorical qualifications5+ years of experience in handling Web technology projectsIntermediate Level, Working experience on C#, ASP, Asp.NET, Perl, MS SQL Server, My SQL, OracleStrong debugging skills, Problem Solving skillsI will bevery glad if i will able to help bugzilla team to improve the product.Regards Sunil JoshiDear developers! Get Yourself a cool, short @in.com Email ID now!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bugzilla.org/pipermail/developers/attachments/20120509/eb1027b5/attachment.html>

From gdsotirov at dir.bg  Sun May 27 16:16:04 2012
From: gdsotirov at dir.bg (Georgi D. Sotirov)
Date: Sun, 27 May 2012 19:16:04 +0300
Subject: ANN: Bugzilla-bg 4.2.1, 4.0.6 and 3.6.9
Message-ID: <mNWdne9jIvjZzl_SnZ2dnUVZ_rednZ2d@mozilla.org>

Hello all,

The latest localizations of Bugzilla in Bulgarian are already available
from OpenFMI (http://openfmi.net/frs/?group_id=76) or my personal FTP
(ftp://sotirov-bg.net/pub/contrib/mozilla/bugzilla/l10n/).

I would like to inform you, that the translation is back on track after
I had some trouble with 4.2 (incidentally broken template) and delayed
the release much.

P.S. If someone could update Bugzilla's download page
(http://www.bugzilla.org/download/#localizations) it would be great!
Thanks in advance!


Best Regards,

-- 
Georgi D. Sotirov
Bugzilla's totalizator in Bulgarian
_______________________________________________
dev-apps-bugzilla mailing list
dev-apps-bugzilla at lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-apps-bugzilla


From lpsolit at gmail.com  Sun May 27 16:42:45 2012
From: lpsolit at gmail.com (=?ISO-8859-1?Q?Fr=E9d=E9ric_Buclin?=)
Date: Sun, 27 May 2012 18:42:45 +0200
Subject: ANN: Bugzilla-bg 4.2.1, 4.0.6 and 3.6.9
In-Reply-To: <mNWdne9jIvjZzl_SnZ2dnUVZ_rednZ2d@mozilla.org>
References: <mNWdne9jIvjZzl_SnZ2dnUVZ_rednZ2d@mozilla.org>
Message-ID: <4FC25985.8020804@gmail.com>

Le 27. 05. 12 18:16, Georgi D. Sotirov a ?crit :
> P.S. If someone could update Bugzilla's download page
> (http://www.bugzilla.org/download/#localizations) it would be great!

Done!

Nice to see you back. :)


LpSolit