PowerShell Scripting to Replicate Bugzilla Data to MySQL

The CData Cmdlets for Bugzilla offer live access to Bugzilla data from within PowerShell. Using PowerShell scripts, you can easily automate regular tasks like data replication. This article will walk through using the CData Cmdlets for Bugzilla and the CData Cmdlets for MySQL in PowerShell to replicate Bugzilla data to a MySQL database.

After obtaining the needed connection properties, accessing Bugzilla data in PowerShell and preparing for replication consists of four basic steps.

You can authenticate to your Bugzilla account using two parameters:

• URL: The URL of your Bugzilla developer's page (the Home page).
• ApiKey: API Keys can be generated from the Preferences -> API Keys section of your Bugzilla developer's page.

Collecting Bugzilla Data

1. Install the module:

   Install-Module BugzillaCmdlets

2. Connect to Bugzilla:

   $bugzilla = Connect-Bugzilla -Url $Url -APIKey $APIKey

3. Retrieve the data from a specific resource:

   $data = Select-Bugzilla -Connection $bugzilla -Table "Bugs"

   You can also use the Invoke-Bugzilla cmdlet to execute pure SQL-92 statements:

   $data = Invoke-Bugzilla -Connection $bugzilla -Query 'SELECT * FROM Bugs WHERE Creator = @Creator' -Params @{'@Creator'='user@domain.com'}

4. Save a list of the column names from the returned data.

   $columns = ($data | Get-Member -MemberType NoteProperty | Select-Object -Property Name).Name

Inserting Bugzilla Data into the MySQL Database

With the data and column names collected, you are ready to replicate the data into a MySQL database.

1. Install the module:

   Install-Module MySQLCmdlets

2. Connect to MySQL, using the server address and port of the MySQL server, valid user credentials, and a specific database with the table in which the data will be replicated:

   $mysql = Connect-MySQL -User $User -Password $Password -Database $Database -Server $Server -Port $Port

3. Loop through the Bugzilla data, store the values, and use the Add-MySQL cmdlet to insert the data into the MySQL database, one row at a time. In this example, the table will need to have the same name as the Bugzilla resource (Bugs) and to exist in the database.

   $data | % { $row = $_ $values = @() $columns | % { $col = $_ $values += $row.$($col) } Add-MySQL -Connection $mysql -Table "Bugs" -Columns $columns -Values $values }

You have now replicated your Bugzilla data to a MySQL database. This gives you freedom to work with Bugzilla data in the same way that you work with other MySQL tables, whether that is performing analytics, building reports, or other business functions.

Notes

• Once you have connected to Bugzilla and MySQL in PowerShell, you can pipe command results to perform the replication in a single line:

  Select-Bugzilla -Connection $bugzilla -Table "Bugs" | % { $row = $_ $values = @() $columns | % { $col = $_ $values += $row.$($col) } Add-MySQL -Connection $mysql -Table "Bugs" -Columns $columns -Values $values }

• If you wish to replicate the Bugzilla data to another database using another PowerShell module, you will want to exclude the Columns, Connection, and Table columns from the data returned by the Select-Bugzilla cmdlet since those columns are used to help pipe data from one CData cmdlet to another:

  $columns = ($data | Get-Member -MemberType NoteProperty | Select-Object -Property Name).Name | ? {$_ -NotIn @('Columns','Connection','Table')}