Scheduling Phase 1 of the GitLab migration

By hestenet on 30 March 2019

Change record status:

Published (View all published change records)

Project:

Issue links:

https://www.drupal.org/node/3002827

Description:

We recently announced our partnership with GitLab to power the developer tools on Drupal.org. This will be a multi-phase process. In the first phase we'll be replacing the current Git backend as well as the code viewing tools with GitLab. The team is currently evaluating the latest release of GitLab and testing our migration process, before scheduling a migration window.

Production outage: There will be an outage window for git pushes
Change affects: Drupal.org Git Services
Deployment schedule: Mar 29th 2019 22:00 UTC – Mar 30th 01:00 UTC (Mar 29th 2019 3pm PDT – 6pm PDT)
Backout plan: revert or fix in place
Status:Deployed

Comments

Provisionally scheduled for

markmangoba commented 9 February 2019 at 00:53

Provisionally scheduled for the week of Feb 25 or March 4. The Engineering team is going through a production readiness check and hope to have that done in the next week.

GitLab phase 1 scheduled

markmangoba commented 8 March 2019 at 04:50

GitLab phase 1 scheduled: Mar 29th 2019 22:00 UTC – Mar 30th 01:00 UTC (Mar 29th 2019 3pm PDT – 6pm PDT)

We are scheduled to deploy GitLab phase 1 on March 29th from 3pm PDT - 6pm PDT. We have made every effort to minimize downtime for the community.

For the past 18 months, interoperability between the current Git infrastructure and migration to GitLab was a much larger effort than expected. With several challenges: optimization of project syncing, disaster recovery, replication, high availability, and phasing out our old Git servers to name a few. Each member of the Engineering Team has put a lot of time and effort in testing and these challenges. We can now confidently say we are ready for launch! We thank GitLab, the Drupal Association Engineering Team, and Partners for helping us achieve this launch date.
I hope you are excited as we are in achieving this milestone.

The goals of phase 1 are:
1. Transparently replace Drupal’s current underlying Git infrastructure (as part of this migration git.drupal.org’s SSH host key will change) for: repository hosting, maintainer permissions, code viewing with GitLab repositories, GitLab roles and permissions for maintainers, and the GitLab code viewing UI.
2. Enable inline code editing for project maintainers.
3. To unblock allowing pull requests, inline code editing for all contributors, and more in phase 2.

Read more about the Drupal Association partnership with GitLab at: https://www.drupal.org/drupalorg/blog/developer-tools-initiative-part-5-...

Please feel free to review our FAQ’s about GitLab at: https://www.drupal.org/drupalorg/docs/gitlab-integration/gitlab-frequent...

If you have questions, please join us in Drupal Slack on channel #gitlab.