Skip to content
GitLab

jira to gitlab migration · Changes

Page history
Update jira to gitlab migration authored by bgm's avatar bgm
Hide whitespace changes
Inline Side-by-side
jira-to-gitlab-migration.md
View page @ 53e5cb93
...@@ -3,6 +3,7 @@ Random thoughts on migrating the main 'CRM' project to Gitlab vs Github: ...@@ -3,6 +3,7 @@ Random thoughts on migrating the main 'CRM' project to Gitlab vs Github:
* Github will not allow us to import the comment history while keeping the author intact. i.e. all comments will be imported as the same user. * Github will not allow us to import the comment history while keeping the author intact. i.e. all comments will be imported as the same user.
* By controlling registration (on civicrm.org), we can keep Community Profiles and better engage with the community/developers. * By controlling registration (on civicrm.org), we can keep Community Profiles and better engage with the community/developers.
* One of the main advantages of Github is that "everyone has an account", so it makes small contributions easier. However, currently CiviCRM currently requires going through a few hoops in order to submit a patch. By opting for Gitlab, we are only slightly simplifying the process (and improving the experience because of a better UI/UX). However, we make it easier to then participate in the other working-groups on Gitlab (it's unlikely we would ever move everything on Github). * One of the main advantages of Github is that "everyone has an account", so it makes small contributions easier. However, currently CiviCRM currently requires going through a few hoops in order to submit a patch. By opting for Gitlab, we are only slightly simplifying the process (and improving the experience because of a better UI/UX). However, we make it easier to then participate in the other working-groups on Gitlab (it's unlikely we would ever move everything on Github).
* Gitlab is Free Software (although Open Core, where its business model is backed by en enterprise version, but they are also very supportive of FOSS projects using Gitlab). JIRA and Github are proprietary. This goes in contraction with CiviCRM's argument that "you own your CRM/data".
* Gitlab could be useful for extensions: * Gitlab could be useful for extensions:
* Vendor-neutral dev spaces (shops could still promote their consulting/support services, like they do on drupal.org, but it would not be in the canonical URL of the git repo). * Vendor-neutral dev spaces (shops could still promote their consulting/support services, like they do on drupal.org, but it would not be in the canonical URL of the git repo).
* Gitlab templates could potentially run civix automatically? hook into gitlab's c-i to run tests? (instead of Jenkins) * Gitlab templates could potentially run civix automatically? hook into gitlab's c-i to run tests? (instead of Jenkins)
...@@ -10,6 +11,7 @@ Random thoughts on migrating the main 'CRM' project to Gitlab vs Github: ...@@ -10,6 +11,7 @@ Random thoughts on migrating the main 'CRM' project to Gitlab vs Github:
General notes for migrating non-CRM JIRA projects (ex: INFRA): General notes for migrating non-CRM JIRA projects (ex: INFRA):
* Script used: https://gist.github.com/florisb/1266d3584dbfdbd2a8a55d31e2518edd * Script used: https://gist.github.com/florisb/1266d3584dbfdbd2a8a55d31e2518edd
* See also: https://about.gitlab.com/2017/08/21/migrating-your-jira-issues-into-gitlab/
* The Gitlab user must be a Gitlab admin * The Gitlab user must be a Gitlab admin
* Get the Gitlab user token from https://lab.civicrm.org/profile/account (i.e. global token, not app-token). * Get the Gitlab user token from https://lab.civicrm.org/profile/account (i.e. global token, not app-token).
* Add the users to the destination project (preferably as 'admins' to avoid permission problems). * Add the users to the destination project (preferably as 'admins' to avoid permission problems).
......