You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Code to migrate Bugzilla (version 4.0.2) to GitHub issues
4
+
and other stuff that happened after that.
3
5
4
6
# Introduction
5
-
For years all bugs have been managed using Bugzilla on bugs.libreplan.org
6
-
For several reasons this however is coming to an end.
7
-
8
-
The succesor is going to be GitHub Issues.
9
-
10
-
This means all current issues need to be transfered to GitHub Issues.
11
-
12
-
For this GitHub has a special REST API
13
-
14
-
# How to go from Bugzilla to GitHub Issues
15
-
There are several steps to consider
16
-
- How to retrieve from Bugzilla: we chose to use a direct database connection
17
-
- How to upload issues to GitHub: we chose to use a special GitHub API
18
-
- How to handle assignees: Chosen to reset to empty
19
-
- How to handle attachments: Since the GitHub API does not support adding attachments there are several options:
20
-
- It is possible to manually upload attachments to issues. At over 500 attachments this was not a really an option.
21
-
- There is an unmaintained ruby script to upload files to GitHub. Decided not to use it.
22
-
- Since the migration is only done once we can dump all attachments to a subdirectory, upload that to a repo and generate a link to the file in the issue comments. So that is what we will do.
23
-
- Yes, we could do fancy "if already exist..." etc, but this is a one off, so we simply add issues.
24
-
25
-
# Sources of inspiration
26
-
GitHub description of API: https://gist.github.com/jonmagic/5282384165e0f86ef105
Code to migrate Bugzilla (version 4.0.2) to GitHub issues
3
+
4
+
## Introduction
5
+
For years all bugs have been managed using Bugzilla on bugs.libreplan.org
6
+
For several reasons this however is coming to an end.
7
+
8
+
The succesor is going to be GitHub Issues.
9
+
10
+
This means all current issues need to be transfered to GitHub Issues.
11
+
12
+
For this GitHub has a special REST API
13
+
14
+
## How to go from Bugzilla to GitHub Issues
15
+
There are several steps to consider
16
+
- How to retrieve from Bugzilla: we chose to use a direct database connection
17
+
- How to upload issues to GitHub: we chose to use a special GitHub API
18
+
- How to handle assignees: Chosen to reset to empty
19
+
- How to handle attachments: Since the GitHub API does not support adding attachments there are several options:
20
+
- It is possible to manually upload attachments to issues. At over 500 attachments this was not a really an option.
21
+
- There is an unmaintained ruby script to upload files to GitHub. Decided not to use it.
22
+
- Since the migration is only done once we can dump all attachments to a subdirectory, upload that to a repo and generate a link to the file in the issue comments. So that is what we will do.
23
+
- Yes, we could do fancy "if already exist..." etc, but this is a one off, so we simply add issues.
24
+
25
+
## Sources of inspiration
26
+
GitHub description of API: https://gist.github.com/jonmagic/5282384165e0f86ef105
0 commit comments