bugzilla2gitlab

Introduction
Installation
Usage
How it works
Caveats
Demo
Contributing

About this fork
This fork is based on https://github.com/xmunoz/bugzilla2gitlab and the great work of @xmunoz. It was adapted and improved to migrate bugs from https://bugs.eclipse.org to https://gitlab.eclipse.org. A list of the changes can be found here: CHANGELOG.md

Introduction

This is a tool for developers or admins who want to migrate the issue management for their software project from Bugzilla to GitLab Issues. Here is a screenshot of an issue created by bugzilla2gitlab:

bugzilla2gitlab copies over bugs, bug comments and attachments.

Installation

This library is very much under development. That said, if you like to feel the wind in your hair, simply pip install bugzilla2gitlab.

More than likely, you will need to roll up your sleeves and hack on the package to achieve a migration that you are happy with. In this case:

git clone git@github.com:xmunoz/bugzilla2gitlab.git
cd bugzilla2gitlab
python3 -m venv venv
source venv/bin/activate
pip install -r requirements.txt
# installs this package locally
pip install .

bugzilla2gitlab is compatible with Python 3.6, 3.7, 3.8, and 3.9.

Usage

bugzilla2gitlab synchronously migrates a user-defined list of bugzilla bugs to a single GitLab project. There are two interfaces for this library. The command line usage:

$  bin/bugzilla2gitlab -h
usage: bugzilla2gitlab [-h] [FILE] [CONFIG_DIRECTORY]

Migrate bugs from Bugzilla to GitLab Issues.

positional arguments:
  [FILE]              A file containing a list of Bugzilla bug numbers to
                      migrate, one per line.
  [CONFIG_DIRECTORY]  The directory containing the required configuration
                      files.

optional arguments:
  -h, --help          show this help message and exit

This package can also be used as a python module.

from bugzilla2gitlab import Migrator

client = Migrator(config_path="/path/to/config")
bugs_list = [1,2,3,4,5,6,7]
client.migrate(bugs_list)

Configuration

To begin using bugzilla2gitlab, the following list of configuration files is required in the specified config directory:

defaults.yml: Core default values used throughout the modules.
user_mappings.yml: key, value pairs of Bugzilla usernames to GitLab users
component_mappings.yml: key, value pairs of Bugzilla components to GitLab labels

Samples of all of these files with documentation for each configuration variable can be found in tests/test_data/config.

bugzilla2gitlab creates issues and comments in GitLab with the user accounts specified in user_mappings.yml, preserving the integrity of the original Bugzilla commenter. This, however, may not always be possible. In tests/test_data/config/user_mappings.yml, users with the designation "bugzilla" may have left the organization and therefore not have current GitLab accounts, or might simply be machine users. Comments for such users will be left under a generic "bugzilla" account. bugzilla2gitlab doesn't create any new user accounts. All of the accounts specified in user_mappings.yml must already exist in your GitLab installation.

The default table created in the issue description by bugzilla2gitlab looks like this:


Bugzilla Link	570755
Created on	Jun 08, 2010 10:25
Version	unspecified
OS	All
Architecture	All
Attachments	a_PHP_play_script_to_demonstrate_how_the_browser_requests_videos
Reporter	mozilla

To modify this table, take a look at create_description in models.py.

How it works

GitLab

GitLab has a comprehensive and extensively documented API. Here are the main endpoints that this library makes use of.

Calls to the GitLab API must be made with an administrator private token in order to impersonate other users.

Bugzilla

This program relies on being able to fetch bug data by simply appending &ctype=xml to the end of the bugzilla bug URL, and then parsing the resulting XML. If this trick doesn't work on your bugzilla installation, then bugzilla2gitlab probably won't work for you.

Caveats

Every comment or mention in GitLab typically sends a notification. This is true even for comments/issues created programmatically. To avoid users inboxes being flooded with meaningless email notifications and avoid overwhelming your SMTP servers, GitLab users should disable all email notifications (global and group-specific) just prior to the running of this script. This can be done through the GitLab UI.

Further, this tools requires GitLab sudo. If you need a tool that works without sudo, take a look at FreeDesktop's migration tool.

Demo

If you want to test out this library on a non-production GitLab instance, I recommend starting up a one-click GitLab droplet from DigitalOcean. From there, you can create a code repository, add some user accounts, and take bugzilla2gitlab for a spin.

Docker image

If you do not want to mess with Python environments in your local installation, you can use a Docker environment to develop and run bugzilla2gitlab.

Clone the Git repo: git clone https://github.com/fredg02/bugzilla2gitlab.git
Build Docker image: ./build_image.sh
Run bugzilla2gitlab in container:
```
run_container.sh
```
- The Git repo is mapped to the directory /bugzilla2gitlab inside the container
- The config directory is mapped to /bugzilla2gitlab/config. It should contain the following files:
  - defaults.yml (copy from tests/test_data/config/defaults.yml and modify)
  - component_mappings.yml
  - user_mappings.yml
  - bugs (optional, if fetch_bugs is not used)
Alternatively, you can start the container with:
```
start_container.sh
```
and inside it, run
```
bin/bugzilla2gitlab
```

Contributing

Check out CONTRIBUTING.md.

fredg02 / bugzilla2gitlab