... | ... | @@ -4,8 +4,6 @@ reference. |
|
|
|
|
|
# GitLab migration
|
|
|
|
|
|
## Migration
|
|
|
|
|
|
GitLab was migrated from Trac in June 2020, after a few months of
|
|
|
testing. Tests were done first on a server called
|
|
|
`dip.torproject.org`, a reference to `salsa.debian.org`, the GitLab
|
... | ... | @@ -14,7 +12,7 @@ merge requests](https://gitlab.torproject.org/tpo/tpa/services/-/issues/32197) d |
|
|
the "GitLab Omnibus" package on the current server, `gitlab-02` which
|
|
|
will enter production in the week of June 15th 2020.
|
|
|
|
|
|
### Why migrate?
|
|
|
## Why migrate?
|
|
|
|
|
|
We're hoping gitlab will be a good fit because:
|
|
|
|
... | ... | @@ -32,7 +30,7 @@ We're hoping gitlab will be a good fit because: |
|
|
of gitlab. There is an "enterprise" version with additional features, but we
|
|
|
prefer to use free software whenever possible.)
|
|
|
|
|
|
### Migrated content
|
|
|
## Migrated content
|
|
|
|
|
|
The issues and wiki of the "Tor" project are migrated. There are no
|
|
|
other projects in Trac.
|
... | ... | @@ -48,7 +46,7 @@ looking for their old stuff. |
|
|
All the tickets that were *not* moved to their respective projects
|
|
|
have been closed in the first week of july.
|
|
|
|
|
|
### Not migrated
|
|
|
## Not migrated
|
|
|
|
|
|
We are *not* migrating away from Gitolite and Jenkins just yet. This
|
|
|
means those services are still fully operational and their equivalent
|
... | ... | @@ -77,7 +75,7 @@ The priority of those features would be: |
|
|
Those are each large projects and will be undertaken at a later stage,
|
|
|
progressively.
|
|
|
|
|
|
### Feature equivalence
|
|
|
## Feature equivalence
|
|
|
|
|
|
| Feature | Trac | GitLab | Comments |
|
|
|
| ------- | ---- | ------ | -------- |
|
... | ... | @@ -134,7 +132,7 @@ Notes: |
|
|
project, but because project creation requires an admin
|
|
|
intervention, this never concretized.
|
|
|
|
|
|
### Ticket fields equivalence
|
|
|
## Ticket fields equivalence
|
|
|
|
|
|
| Trac | GitLab | Comments |
|
|
|
| ---- | ------ | -------- |
|
... | ... | @@ -161,7 +159,7 @@ Notes: |
|
|
Notice how the `Label` field is used as a fallback when no equivalent
|
|
|
field exists.
|
|
|
|
|
|
### Missing features
|
|
|
## Missing features
|
|
|
|
|
|
GitLab does not provide one-to-one feature parity with Trac, but it
|
|
|
comes pretty close. It has issue tracking, wikis, milestones,
|
... | ... | @@ -186,7 +184,7 @@ needing to request approval on a per-person basis for now. Eventually, |
|
|
we're going to consider other options to work around this (human)
|
|
|
bottleneck.
|
|
|
|
|
|
### Interesting new features
|
|
|
## Interesting new features
|
|
|
|
|
|
1. Using pull requests to your project repositories, and assigning
|
|
|
reviewers on pull requests, rather than using `reviewer` and
|
... | ... | @@ -216,7 +214,7 @@ bottleneck. |
|
|
receive from Gitlab, and Gitlab will put your responses into the system as
|
|
|
notes on issues :-)
|
|
|
|
|
|
### bugs.torproject.org redirections
|
|
|
## bugs.torproject.org redirections
|
|
|
|
|
|
The <https://bugs.torproject.org> redirection now points at
|
|
|
GitLab. The following rules apply:
|
... | ... | @@ -242,7 +240,7 @@ we decided against it because it would forbid pointers to |
|
|
user-specific projects and would make it extremely hard to switch away
|
|
|
from the global `tpo` group if we ever decide to do that.
|
|
|
|
|
|
### Content organisation
|
|
|
## Content organisation
|
|
|
|
|
|
Projects are all stored under the over-arching `tpo` group. This is
|
|
|
done this way to allow project managers to have an overview of all
|
... | ... | @@ -252,7 +250,7 @@ organisations on our GitLab in a different namespace. |
|
|
Under the `tpo` group, each team has its own subgroup and they have
|
|
|
autonomy under that group to manage accesses and projects.
|
|
|
|
|
|
### Permissions
|
|
|
## Permissions
|
|
|
|
|
|
Given the above Team/Group organization, users will be members in
|
|
|
gitlab for the groups/teams they belong to.
|
... | ... | @@ -278,7 +276,7 @@ A reminder of the GitLab [permission system](https://docs.gitlab.com/ee/user/per |
|
|
team. They can also transfer projects to other name spaces, switch
|
|
|
visilbity level, delete issues.
|
|
|
|
|
|
### Labels
|
|
|
## Labels
|
|
|
|
|
|
At group level we have sponsor labels and state labels. The ones that
|
|
|
are used by the whole organization are in the `tpo` group. Each team
|
... | ... | @@ -317,7 +315,7 @@ deleted labels in one batch in all projects. When the job was done, |
|
|
A [dump of the previous state](https://gitlab.torproject.org/ahf/label-cleanup/-/raw/main/tpo/core/tor-history.yaml) is available for historical
|
|
|
purposes.
|
|
|
|
|
|
### Project organisation
|
|
|
## Project organisation
|
|
|
|
|
|
It is recommended that each team sets up a `team` project which can
|
|
|
welcome issues from outside contributors who might not otherwise know
|
... | ... | @@ -329,11 +327,11 @@ will have to be manually migrated to the respective teams. |
|
|
|
|
|
This organisation is still being discussed, see [issue 28](https://gitlab.torproject.org/tpo/tpa/gitlab/-/issues/28).
|
|
|
|
|
|
### Git repository migration
|
|
|
## Git repository migration
|
|
|
|
|
|
Git repository migration is still being discussed, in [ticket 36](https://gitlab.torproject.org/tpo/tpa/gitlab/-/issues/36).
|
|
|
|
|
|
### What will break, and when will you fix it?
|
|
|
## What will break, and when will you fix it?
|
|
|
|
|
|
Most notably, we're going to have an interruption in the ability to open new
|
|
|
accounts and new tickets. We _did not_ want to migrate without a solution
|
... | ... | @@ -350,7 +348,7 @@ have to adjust our workflows to work around this. In some cases, we can use |
|
|
gitlab milestone pages or projects that do not need a wiki page as a work
|
|
|
around.
|
|
|
|
|
|
### Trac Archival
|
|
|
## Trac Archival
|
|
|
|
|
|
A copy of all Trac web pages were stored in the [Internet
|
|
|
Archive](http://archive.org/)'s [Wayback machine](http://web.archive.org/), thanks to [ArchiveBot](https://www.archiveteam.org/index.php?title=ArchiveBot), a tool
|
... | ... | @@ -410,7 +408,7 @@ This information can be extracted back again from the `*-meta.warc.gz` |
|
|
40003](https://gitlab.torproject.org/tpo/tpa/services/-/issues/40003). There has also been other, independent, crawls of Trac,
|
|
|
which are partly visible [in the viewer](https://archive.fart.website/archivebot/viewer/?q=trac.torproject.org).
|
|
|
|
|
|
### History
|
|
|
## History
|
|
|
|
|
|
* lost in the mists of time: migration from Bugzilla to Flyspray (40
|
|
|
tickets)
|
... | ... | |