Re: [cdt-dev] automation of policy violations in bugzilla

[Elena Laskavaia <elaskavaia@xxxxxxx>]

I am not talking about updates or setting flags automatically. I am talking about "report" like compiler gives you parse errors when you do something wrong.
Like every night a script would run and print report and send to dev-list

Warning 1: bug 123456 is in Fixed state, and has an attached patch which from non-commiter which does not have iplog flag set. Please review and set flag to + or -.
Warning 2: bug 345678 is in Fixed state, but assigned to inbox-*. Please re-open and re-assign to appropriate commiter.

Does it sound reasonable?

Doug Schaefer wrote:
> Yes, more to the point, updates of the database are not allowed from the 
> scripting interface the foundation has given us. So this wouldn't be 
> possible anyway.
>
> Doug
>
> On Thu, Jun 4, 2009 at 12:20 PM, Elena Laskavaia <elaskavaia@xxxxxxx 
> <mailto:elaskavaia@xxxxxxx>> wrote:
>
>     It is all great but if we can automated violation reporting I would.
>     I get that nobody knows about how to make batch requests to bugzilla?
>
>     Doug Schaefer wrote:
>
>         I'm done. I'm not sure an automated script is necessary. The
>         rules in the end are pretty simple. It's just a matter of
>         getting in the habit. Here's what they are:
>
>         1) If you apply a patch or derive from it, mark the patch
>         attachment as iplog+. You need to do an analysis on it anyway to
>         decide whether to IPzilla it so that should be a trigger to set
>         the flag.
>
>         2) Assign the bug to yourself. Again, inboxes can't commit code
>         ;). I am using the assignee to figure out who applied the patch.
>         If a bug has multiple patches applied by different people, then
>         the last one who applied one should be good enough.
>
>         3) Set the target milestone to the next one available. We need
>         to know what release the patch first appears in.
>
>         This is all stuff we should be doing anyway.
>
>         Thanks,
>         Doug.
>
>         On Wed, Jun 3, 2009 at 4:44 PM, Elena Laskavaia
>         <elaskavaia@xxxxxxx <mailto:elaskavaia@xxxxxxx>
>         <mailto:elaskavaia@xxxxxxx <mailto:elaskavaia@xxxxxxx>>> wrote:
>
>            Does anybody know how to automate policy enforcement in bugzilla?
>            (Such as iplog flag should be set on contributor patch if pr is
>            fixed kind of)
>            Poor Doug setting iplog flags for a week now...
>            If we can have a script that runs overnight and send us report of
>            violations it would be a lot better for next time around
>            (assuming we cleaned it up now it would very small number of
>         items)
>            and responsible
>            persons would fix that themselves...
>
>            _______________________________________________
>            cdt-dev mailing list
>            cdt-dev@xxxxxxxxxxx <mailto:cdt-dev@xxxxxxxxxxx>
>         <mailto:cdt-dev@xxxxxxxxxxx <mailto:cdt-dev@xxxxxxxxxxx>>
>
>            https://dev.eclipse.org/mailman/listinfo/cdt-dev
>
>
>
>         ------------------------------------------------------------------------
>
>
>         _______________________________________________
>         cdt-dev mailing list
>         cdt-dev@xxxxxxxxxxx <mailto:cdt-dev@xxxxxxxxxxx>
>         https://dev.eclipse.org/mailman/listinfo/cdt-dev
>
>     _______________________________________________
>     cdt-dev mailing list
>     cdt-dev@xxxxxxxxxxx <mailto:cdt-dev@xxxxxxxxxxx>
>     https://dev.eclipse.org/mailman/listinfo/cdt-dev
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev