I recently released a new version of the Bazaar plugin for Jenkins. This release was inspired by a problem we noticed at Percona. It is:

• run “bzr revert” after a pull, as if you have a directory that is removed and re-added while having unknown files in said directory (e.g. build artifacts), you would end up in a very bad place (this is a BZR bug, so we work-around it with a “bzr revert”).

The update has already appeared in the Jenkins update centre, so you should already be able to upgrade to it.

From the desk of your new Bazaar plugin for Jenkins maintainer, I give you Version 1.18.

This release has two good bug fixes:

• UI fix for checkout option (JENKINS-12261)
• Auto-recover from corrupt BZR branches (e.g. bzr branch/checkout killed at inopportune moment) by cleaning the workspace and trying again (this is now default behaviour, best used with the Jenkins SCM retry count feature being > 1)

We’ve been running the same code as this release at Percona for about 2 months now (the second bugfix was one I wanted to test first before submitting upstream). This is the big fix that fixed all our problems with using bazaar with Jenkins in a large deployment.

For Drizzle and for all of the projects we work on at Percona we use the Bazaar revision control system (largely because it’s what we were using at MySQL and it’s what MySQL still uses). We also use Jenkins.

We have a lot of jobs in our Jenkins. A lot. We build upstream MySQL 5.1, 5.5 and 5.6, Percona Server 5.1, Percona Server 5.5, XtraBackup 1.6, 2.0 and 2.1. For each of these we also have the normal trunk builds as well as parameterised ones that allow a developer to test out a tree before they ask for it to be merged. We also have each of these products across seven operating systems and for each of those both x86 32bit and 64bit. If we weren’t already in the

Not counting obtaining the source code, and once you have the prerequisites satisfied, [Windows] users can build from source code in 5 easy steps.

Prerequisites – Install & ensure they are in the $PATH:

Any re-implementations of this protocol must also be under GPL, unless one has got an license from MySQL AB stating otherwise.

Why a New Utility?

A couple of months back, Tim Procter, Sheeri Cabral and I were discussing about how best to diagnose a MySQL server and/or tune its performance, automating the process as much as possible. The Performance Advisors from MySQL Enterprise (http://www.mysql.com/products/enterprise/) do this, but most of our customers don’t have a subscription and Pythian’s collective experience is not necessary reflected by its rules.

In our daily work, we have used Major Heyden’s MySQL Tuner, Mark Leith’s Statpack and our own tools to review a MySQL server configuration parameters. However, all of these tools had limitations in regards of what we wanted to achieve. Our major

Today at the Riga Sun Database Group Developer Meeting, I'm giving a MySQL University session about using Launchpad.net and Bazaar for Contributors. Below, I've posted links to the slides.

A Contributor's Guide to Launchpad and Bazaar

Topics included in the slides:

• Getting started on Launchpad
• Various features of Launchpad

When Brian began the work on refactoring the MySQL 6.0 Server source code into what has now become the Drizzle Project, a number of code pieces were removed, including some major MySQL functionality such as stored procedures, server-side prepared statements, SQL Mode, some legacy code, and a variety of data types. The goal, of course, was to reduce the server code base down to a more streamlined and eventually modular kernel.

Of course, that vision is great, but it's got some side effects! One of those side effects is a dramatic reduction in the number of test cases that pass the test suite in their current form, and an increase in the number of tests that have been disabled. I re-enabled and fixed a few tests yesterday, but as of this writing, there are only 54 of

Attention MySQL engineers and Drizzle contributors: upgrade to Bazaar 1.6.1 now to get some fairly massive performance speedups for bzr branch commands. As I noted in my last article on Launchpad code management, Bazaar 1.5 was having some performance issues when branching large project trees such as MySQL. In the article, I showed it was taking Bazaar 1.5 91 minutes to do the initial branch. With John Arbash Meinel's performance patches, the time to branch was cut down to 23 minutes, which is a fantastic improvement.

Ubuntu users: grab the 1.6.1 Bazaar package for your Ubuntu version from the Launchpad.net Bazaar Project Package Archive.

Mac OSX users:: grab the

In writing my last article, I mentioned working with John Arbash Meinel, one of the lead developers of Bazaar, in attempting to diagnose and fix the performance bottlenecks apparent in using Bazaar with larger, history-rich projects like the MySQL Server. Well, after running some tests and building a custom branch of Bazaar that John pointed me to, I am happy to tell you that help is just around the corner. In my last article, you saw that doing a bzr branch lp:mysql-server took 91 minutes. This was a significant barrier to entry, I recognize. So, I think you'll be happy to see the results below, taken yesterday using John's patched-up Bazaar branch:

In this second part of my Launchpad guidebook series, I'll be covering the code management and repository features of Launchpad.net. If you missed the first part of my series, go check it out and get established on Launchpad.net. Then pop back to this article to dive into the magic of http://code.launchpad.net. In this article, we'll cover the following aspects of the code management pieces of Launchpad:

• The Structure of Project Source Code on Launchpad.net
• Pulling Code into a Local Repository
• Creating a Local Working Branch for Bug Fixing
• Pushing Code to Launchpad
• Notifying a Merge Captain of Your Code Pushes
• Keeping

This post is the first in a series of articles which serves to highlight the services of the Launchpad platform which hosts the MySQL Server, MySQL Forge, MySQL Sandbox and Drizzle Server projects. I will be walking you through the various pieces of the platform and provide examples of using each of the services. I will cover in depth the source code management services which all three projects now rely upon. The code management services are the critical piece of the development platform. In addition, I will show you how to use the Blueprints, Bugs, Answers and Translations services that many MySQL ecosystem projects,

Looks like drizzle is announced now. I’ve spent a bit of time after work and on lunch breaks helping out here and there, and I’m excited about working on a database project again. Why am I working on the project? Average time from when I write a patch to when it goes into the tree has been measured in minutes, not in hours/days/weeks/months. Yes, I’m running the test suite first. Yes, I’m getting another person to review the code first. This is an example of how adding people to a project can slow it down, and how getting out of the way of the engineers can have amazing results. We set up bug tracker, code hosting, team organization, package build system,

There is some very big news going around that internet thing today: MySQL has switched from Bitkeeper to Bazaar. I wrote up a quick post on the Canonical blog about the same thing, and Giussepe Maxia has a nice technical post about how to get started working with the new system.

Here’s an excerpt from a mail I just sent to an internal Canonical list:

Bazaar and Launchpad are truly tools that matter, from a historical and social perspective. MySQL and other open source software run a huge percentage of the internet, and these tools preserve and enrich the body of knowledge that is in the public commons, knowledge that

And here we are, my second post in which I mention twitter, and wonder aloud what open source software projects should be doing with twitter. I don’t have any well-formed thoughts to foist on you, but I’ll tell you about an experiment I’ve been doing. Last week I started using summize.com to search for conversations about bzr. I did the same thing for ubuntu and for git, but only really stuck with the bzr stream. It’s been interesting to see what people are talking about, I’ve tried chiming in with suggestions when I can or asking for further details when people complain. I think what is so fascinating to me about this is that I’m finding a whole lot of conversations that aren’t at the level of a ranting blog post but are encouraging or thought-provoking feedback nonetheless.

I also