This video outlines the migration phases that we discussed in the announcement of our partnership with GitLab. Our migration window for Phase 1 is targeted for the first weeks of January, and we hope Phase 2 to be completed shortly in the beginning of 2019.
So what has it taken to get this integration working between September and now?
- Primarily, lots of collaboration from the GitLab team. We’ve worked with their excellent engineering staff to resolve a number of issues that affect our integration, including:
- git merge-base web api
- Add ability to confirm a user’s email address via “Add email for user” API
- Allow configuration of the display URL for clone instructions
- Ability to hide User’s Email Address from GitLab UI
- Allow ability for developer role to delete tags
- Set GL_REPOSITORY in update hooks for API-initiated requests
- Deduplication of git objects, reducing disk space of repository forks
- On the Drupal.org side, we’ve built a versioncontrol_gitlab module, which extends our use of the versioncontrol_git module to orchestrate our integration.
- We’ve also been cleaning up our data, to ensure there are no namespace conflicts between existing Drupal projects and users, and the reserved terms used by GitLab.
We’re now in the midst of serious migration testing. Testing and re-testing the process in our staging environment, putting load testing in place to stress test our integration, and doing user-validation testing to ensure that the workflows affected by this integration are working as expected.
All in all, we’re thrilled with the progress, and very thankful for GitLab’s close collaboration. We’re excited to be moving the Drupal project to its next generation tooling soon. Once Phase 1 of our migration is complete, it’ll be time for Phase 2 and our community will start seeing some tremendous improvements in efficiency and collaboration.
Drupal Association – Executive Director