autobuilds and bug tracker

autobuilds and bug tracker

[Rolf Leggewie]

Hi,

I'd like to ask the people doing the autobuilds for a simple, yet
important change when reporting failures to the bug tracker and
attaching logs.

current situation

 Description: Build log
 Comment: The package failed to build at $date for machine $device

I think the following makes the attachment box at the top of the report
more informative

 Description: Build log for machine $device
 Comment: The package failed to build at $date

or even better

 Description: Build log for machine $device
 Comment: The package $package failed to build at $date in $task

Could that be done?

BTW, I saw that logs are not always attached.  Is that intended behaviour?

Best

Rolf

Re: autobuilds and bug tracker

[Junqian Gordon Xu]

On 02/22/2008 09:43 AM, Rolf Leggewie wrote:
> I'd like to ask the people doing the autobuilds for a simple, yet
> important change when reporting failures to the bug tracker and
> attaching logs.

I would also like to be able to opt out of receiving emails from 
autobuilder bugs. Something like keeping these bot bugs separate from 
"human" bugs in the bug tracker would also be helpful.

Regards
Gordon

Re: autobuilds and bug tracker

[Rolf Leggewie]

Junqian Gordon Xu wrote:
> I would also like to be able to opt out of receiving emails from 
> autobuilder bugs. 

I am not sure what you mean.  I don't receive any of those mails for
example.  The autobuilder always opens a new bug.  So you won't get
mails about that unless you either read all mails to oe-issues (which is
really not a good idea IMHO) or you have added yourself to cc (in which
case the fix should be obvious).

I suggest
a) http://bugs.openembedded.org/userprefs.cgi?tab=email
b) using saved search functions in bugzilla instead of "drinking from
   the firehose".  The search is very powerful.

Re: autobuilds and bug tracker

[Junqian Gordon Xu]

On 02/25/2008 06:36 AM, Rolf Leggewie wrote:
> I am not sure what you mean.  I don't receive any of those mails for
> example.  The autobuilder always opens a new bug.  So you won't get
> mails about that unless you either read all mails to oe-issues (which is
> really not a good idea IMHO) 
> I suggest
> a) http://bugs.openembedded.org/userprefs.cgi?tab=email

Thanks. This helps.

> b) using saved search functions in bugzilla instead of "drinking from
>    the firehose".  The search is very powerful.

comparing to oe-commit, oe-issues is really just a faucet. And seems
there ARE people drinking from the oe-issues firehose, let alone oe-issues.

Regards
Gordon

Re: autobuilds and bug tracker

[Rolf Leggewie]

Rolf Leggewie wrote:
> I'd like to ask the people doing the autobuilds for a simple, yet
> important change when reporting failures to the bug tracker and
> attaching logs.

bump

Re: autobuilds and bug tracker

[Koen Kooi]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Rolf Leggewie schreef:
| Rolf Leggewie wrote:
|> I'd like to ask the people doing the autobuilds for a simple, yet
|> important change when reporting failures to the bug tracker and
|> attaching logs.
|
| bump

Like I said in the staging abi thread:

~  "I'd like to work on improving that, but can't since my bugzilla privs
disappeared under suspicious circumstances...."
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFHzIqFMkyGM64RGpERAs/xAJkBmcgxBOJZmGWy5ijd3+4sJamG0QCeOAtn
DYg0djDhgfElH2cR+NQ8Ugo=
=+z/H
-----END PGP SIGNATURE-----

Re: autobuilds and bug tracker

[Rolf Leggewie]

Hello Koen,

thank you for your reply.

Koen Kooi wrote:
> Like I said in the staging abi thread:
> 
> ~  "I'd like to work on improving that, but can't since my bugzilla privs
> disappeared under suspicious circumstances...."

I tend to think those changes where anything but suspicious and you were
made aware of the reasons as far as I know.

Furthermore, I don't see why the changes in question would need any
changes to bugzilla itself.  Your accounts as well as
autobuild@openembedded.org can make bug reports like everybody else and
I cannot see why more is needed.  If there are changes to bugzilla
necessary, let me know and I will seek to them being implemented.

Regards

Rolf

Re: autobuilds and bug tracker

[Rolf Leggewie]

Rolf Leggewie wrote:
> Furthermore, I don't see why the changes in question would need any
> changes to bugzilla itself.  

From what I can gather, only seppuku.bbclass would have to be altered.
http://oz.leggewie.org/wip/seppuku.diff.txt may or may not achieve the
result I proposed.

So let me ask again why you need an escalation of privileges before you
can proceed.

Re: autobuilds and bug tracker

[Koen Kooi]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Rolf Leggewie schreef:
| Rolf Leggewie wrote:
|> Furthermore, I don't see why the changes in question would need any
|> changes to bugzilla itself.
|
| From what I can gather, only seppuku.bbclass would have to be altered.
| http://oz.leggewie.org/wip/seppuku.diff.txt may or may not achieve the
| result I proposed.
|
| So let me ask again why you need an escalation of privileges before you
| can proceed.

Well, that's a failry long list, but let me start with:

* managing default values for bugs (e.g. build/distro, distro, priority,
etc)
* adding extra fields for the autobuilder to fill in
* Fixing charset conversion due to our utf8 migration not being complete

and finally, the most important one: tweaking xmlrpc params so we can
stop screenscraping of bugzilla.

regards,

Koen

- --
koen@dominion.kabel.utwente.nl will go go away in december 2007, please
use k.kooi@student.utwente.nl instead.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFHzREYMkyGM64RGpERAgZbAJ9aN4g6jn5ZSbLA1atAF3Tzi1GzVACcDGcq
1T6uhSLReq5RyXNIsFz2Pnc=
=brLy
-----END PGP SIGNATURE-----

Re: autobuilds and bug tracker

[Richard Purdie]

On Tue, 2008-03-04 at 10:06 +0100, Koen Kooi wrote:
> Rolf Leggewie schreef:
> | Rolf Leggewie wrote:
> |> Furthermore, I don't see why the changes in question would need any
> |> changes to bugzilla itself.
> |
> | From what I can gather, only seppuku.bbclass would have to be altered.
> | http://oz.leggewie.org/wip/seppuku.diff.txt may or may not achieve the
> | result I proposed.
> |
> | So let me ask again why you need an escalation of privileges before you
> | can proceed.
> 
> Well, that's a failry long list, but let me start with:
> 
> * managing default values for bugs (e.g. build/distro, distro, priority,
> etc)
> * adding extra fields for the autobuilder to fill in
> * Fixing charset conversion due to our utf8 migration not being complete
> 
> and finally, the most important one: tweaking xmlrpc params so we can
> stop screenscraping of bugzilla.

Hopefully we can review the whole bugzilla permissions situation once it
moves to a new host.

Cheers,

Richard

Re: autobuilds and bug tracker

[Rolf Leggewie]

Rolf Leggewie wrote:
> From what I can gather, only seppuku.bbclass would have to be altered.
> http://oz.leggewie.org/wip/seppuku.diff.txt may or may not achieve the
> result I proposed.

Now that I have done the work to prepare this patch, I wonder if there
is any reason not to apply it.  I'd like to get the issue at hand resolved.

Re: autobuilds and bug tracker

[Koen Kooi]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Rolf Leggewie schreef:
| Rolf Leggewie wrote:
|> From what I can gather, only seppuku.bbclass would have to be altered.
|> http://oz.leggewie.org/wip/seppuku.diff.txt may or may not achieve the
|> result I proposed.
|
| Now that I have done the work to prepare this patch, I wonder if there
| is any reason not to apply it.  I'd like to get the issue at hand
resolved.

Please apply it, I just made other changes to sepukku that will make
autobuild bug management easier.

regards,

Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFH1WWzMkyGM64RGpERAgUsAJ9mddHnz7jnSaOc3o3jNMOGDgtJNQCfR/ck
f9SmoFMPb86o7RKBFldH1hQ=
=1kzu
-----END PGP SIGNATURE-----

Re: autobuilds and bug tracker

[Rolf Leggewie]

Koen Kooi wrote:
> Please apply it, I just made other changes to sepukku that will make
> autobuild bug management easier.

Thank you for your work. I have committed the last two changes I was
looking for as

219fa4485d47101df96e2d47c358fe5617f1f2d8
41716f313f0efdbc890ccb2a7a5d8c24cae3ed69

Please report back if there are any unexpected problems.