Tag Archives: bugzilla

Mandriva Testcases

November 6, 2008

Well, after some discussion on cooker and, quite frankly, needing a resource myself to speed up security update testing (particularly looking for regressions), we’ve re-implemented “Testzilla”. Sorta.

Instead of integrating with bugzilla, we’ve used the mediawiki framework. The reasons for this many. The biggest reason is to make the “Testzilla” as accessible as possible to as many people as possible. It is also to lower the bar to usability… anyone can look at information on the wiki, but dealing with Testzilla can be trickier (perhaps). Also, Testzilla itself hasn’t been updated in many years, which means a lot of hacking to make it work. Other solutions were either too complicated (Testopia) or didn’t integrate with anything else we currently had (using mediawiki allows us to re-use our authentication from my.mandriva.com).

Anyways, the basic idea is to have a page per package (urpmi, eclipse, evolution, whatever) and on this page will be testcases — descriptions of ways to test programs in that package. Where possible, automated or semi-automated testcases should be written and these get committed to subversion and referenced from the wiki page (the downside here is we need a mechanism to get testcases from people without commit access in, but the upside is it is faster, provides versioning, and won’t bog down the wiki with (hopefully!) numerous testcases).

I’ve already implemented the main page, which can be found at wiki.mandriva.com/en/Testing, and from there you can get to the various testcases (there’s only one on there right now). There is a cookie-cutter template to be used to start new testcases pages, and there are some new macros that make integrating with subversion and bugzilla a little easier/nicer.

All in all, I think this has the potential to do really good things for Mandriva, and probably other distributions as well. With the ability for anyone to create testcase pages, testcases, send an email with an automated testcase attached to our new testcases_@_mandrivalinux_dot_org “exploder” to get committed to subversion, it should be extremely easy and straightforward for people to get involved.

This is something that quite a few people on the cooker list expressed an interest in, so I’m hoping this will nicely take off and become yet another useful resource for the Mandriva community.

Also tagged , – 1 Comment

Bugzilla 3.2rc1 is live on qa.mandriva.com

October 26, 2008

Seven weeks ago I setup a local copy of Bugzilla 3.2rc1 to test the upgrade/migration from 3.0.5, using the templates and data from Mandriva’s bugzilla. Tonight it went live on qa.mandriva.com. Although it could have gone up 6 weeks ago, due to the release of 2009.0 coming up (which always leads to a massive influx of bug reports both before and after a release) we decided to wait for a few weeks after 2009.0 was released.

The upgrade went quite smooth (due to the preparation and, most importantly, notes taken from the testing almost two months ago), so everything should be up and running in good order. If there are issues, feel free to comment to me directly or file a bug report. I think, however, that users will find the new version of Bugzilla contains some welcome features and I also took the opportunity to change the layout somewhat to make it adhere more to web standards (such as making font resizing easier, etc.). I also condensed the layout somewhat by using the default Bugzilla templates and re-working them from scratch.

I hope everyone likes it. There will probably be more tweaks coming and rc2 is supposed to be coming out fairly soon from what I’ve heard, so there will still be changes forthcoming, although I hope they are more minor than what changed tonight. I’m also hoping this will improve performance somewhat as Bugzilla 3.2 is using InnoDB rather than MyISAM storage types, which from my understanding should also help improve performance.

Also tagged – 3 Comments

New Mandriva Bugzilla update in the works

September 9, 2008

I’ve spent the entire day yesterday and another day last week working on migrating the current Mandriva bugzilla 3.0.5 to the new 3.2rc1. You won’t see it anywhere official until 2009.0 is released most likely, but having (some) spare time, I wouldn’t to put it through the paces in a vmware machine to make sure I can document everything that needs doing and minimize downtime when it comes time to do the actual upgrade.

So far it’s looking pretty good and has some really nice features to it. Due to the heavy changes in the templates, the templates look more stock now than they did before, which actually manages to clean up a lot of the interface and remove duplicate information. I also took the opportunity to style it as best I can to respect user font sizing. The look has changed a little bit along the way as I had to redo all the theming from scratch.

Anyways, for anyone interested in taking a peek at it or playing around with it a bit before it goes live, you can do so at bugzilla.annvix.ca. It’s a snapshot of the Mandriva database from a week ago (more or less), and uses the same authentication, etc. as the Mandriva bugzilla. To prevent confusion, I’ve turned postfix off so mail notifications aren’t being sent.

All-in-all, the upgrade should go fairly smoothly and result in downtime of an hour or two, when it happens. It could probably be implemented now, but I’d rather wait until 2009.0 is released and things have settled down, so consider this a preview until such a time as it does get moved over. Any suggestions or whatever are also welcome.

Also tagged – 3 Comments

Conspiracy theories unite! Hiding bug reports in bugzilla…

October 20, 2007

I find it quite amusing how quickly people jump the gun on things and start spreading FUD without bothering to talk to the people involved. I suppose that’s the creative license that having a blog entitles people, but it still irks me because in a lot of cases it’s completely unfounded and could easily be cleared up with a simple email question.

I was wandering around and found Battle of the Titans: Mandriva 2008 vs OpenSUSE 10.3. Interesting read; I like how Mandriva comes out on top although there are definitely areas we can improve upon. But what else is new? Every distro has areas that can be improved upon.

Anyways, in the comments I’m reading: “the sad part is an unexpected secrecy in Mandriva”, which refers to a bug aliased as CVE-2007-2834, for which the individual didn’t have access to. Of course, he starts a FUD-based tirade on his own blog Planete Beranger. And this is where the fun begins.

read more »

Also tagged – 2 Comments

Of Bugzilla Clients

September 28, 2006

Michael Scherer posted to cooker@ a few days ago about putting PyBugz a devilishly cool python app for querying a bugzilla database into cooker. He also emailed me because a while ago I had tried the GUI Deskzilla product with the Mandriva bugzilla and it didn’t work, so he mentioned he had made some changes to our bugzilla and it worked with PyBugz and he thought it might work with Deskzilla.

Well, he was wrong, it still doesn’t work with Deskzilla. Our bugzilla is pretty hacked up, so it’s not too surprising.. it seems to me that it deviates quite a bit from standard bugzilla. FWIW, Deskzilla works great with the Annvix bugzilla.

PyBugz, on the other hand, seems to be a great query tool for our bugzilla. It seems to be quite Gentoo-centric (which is ok), so it doesn’t work to post a new bug to bugzilla. It does work to submit a comment to bugzilla, however, and authentication works, which is great. The problem is, as I just discovered, if you submit a comment to a private bug (our “group” feature… I have no idea if this is from bugzilla or something we added, but you can have bugs appear only to certain groups; we use it for hiding security-related issues), it unsets the group flag (effectively making a security-related bug from being private to public). Note to self… do not use PyBugz to post comments to our bugzilla.

But for a query tool it works like a hot damn:

vdanen@odin:~/ >% bugz --base 'http://qa.mandriva.com' search \
--assigned-to warly@mandriva.com
 * Using http://qa.mandriva.com
 * Searching for bugs with the following options:
 *    assigned_to          = warly@mandriva.com
   5856 warly                Services logs are duplicated (ex: LDAP)
   6638 warly                bugzilla asks to login too many times
   7429 warly                MIssing hd.img in 10.0 beta1/beta2/RC1 ISO
...

(the list is pretty long so I’ve truncated it, wc tells me there’s 177 bugs there).

Anyways, I thought I’d mention how slick this thing is… I’m pretty impressed by it. Seems to be a lot faster than trying to use the web interface directly and could also be scriptable to create reports of how good (or bad) people are doing with their bugs (not to mention possibly creating customized daily TODO lists)… the possibilities are pretty limitless.

Oh, for anyone wanting to use this on OS X, you should download the latest python from pythonmac, which is 2.4.3 (fink only has 2.4.2, and OS X 10.4 comes with 2.3.5). You’ll also want to grab the current svn version of PyBugz (it doesn’t work very well with the 0.6 tarball release on the site), and you’ll also need to download ElementTree, which PyBugz requires (very easy to install python module). Install the updated Python first however and make sure the PATH is setup and such appropriatly before installing ElementTree or it could get installed in the wrong place. Once you do that, it’ll work peachy on OS X.

Also tagged , – 2 Comments

Subversion, MediaWiki, and Bugzilla

March 25, 2006

Found this fantastic article about how to setup Subversion, MediaWiki, and Bugzilla to be nicely integrated. The article is really well done, and I’ve adapted most of it to the Annvix wiki and bugzilla, but the subversion integration will be a little problematic (or at least not as full as it could be) because the subversion rep is a copy of the real rep (on that server at least). My real subversion rep is on the build host so it can’t be as tightly integrated. Great article and has helped to knit three different “technologies” together a little better. Anyone who uses all three tools for their project should really take a look at it.

Also tagged , – 6 Comments