In team#41180 (closed) and TPA-RFC-36, we decided to migrate all legacy Git infrastructure (Gitolite and GitWeb) to GitLab. This milestone tracks that progress.

It was split out of the old service retirements 2023 milestone because it was getting unwieldy.

Here's a copy of the timeline from the RFC, T below is 2023-06-08.

Timeline

The migration will happen in four stages:

1. now and for the next 6 months: voluntary migration
2. 6 months later: evaluation and idle repositories locked down
3. 9 months later: TPA enforced migration
4. 12 months later: Gitolite and GitWeb server retirements

T: proposal adopted, voluntary migration encouraged

Once this proposal is standard, Gitolite users are strongly advised to migrate to GitLab, following the migration procedure (#41212, #41219 for TPA repositories, old service retirement 2023 milestone for the others).

Some modification will be done on the gitweb interface to announce its deprecation. Ideally, a warning would also show up in a global pre-receive hook to warn people on push as well (#41211).

The proposal was adopted on June 8th, 2023.

T+6 months: evaluation and idle repositories locked down

After 6 months, TPA will evaluate the migration progress and send reminders to users still needing to migrate (#41214).

TPA will lock Gitolite repositories without any changes in the last two years, preventing any further change (#41213).

This was originally scheduled for December 2023, but has been postponed to January 2024.

Repositories were actually locked down in March 2024.

T+9 months: TPA enforces migration

After 9 months, the migration will be progressively enforced: repositories will be moved or archived to GitLab by TPA itself, with a completion after 12 months (#41215).

Once all repositories are migrated, the redirections will be moved to the static mirror system (#41216).

The retirement procedure for the two hosts (cupani for Gitolite and vineale for GitWeb) will be started which involves shutting down the machines and removing them from monitoring (#41217, #41218). Disks will not be destroyed for three more months.

This is scheduled for March 2024. The mass migration was completed in April 2024, at which point this milestone was marked as completed, as the remaining work is automated. A blog post has been opened in tpo/web/blog#40071 (closed).

T+12 months: complete Gitolite and GitWeb server retirement

After 12 months, the Gitolite (cupani, #41217) and GitWeb (vineale, #41218) servers will be fully retired which implies physical destruction of the disks.

This is scheduled for June 2024. VMs have been actually scheduled for destruction for the end of July 2024.

T+24 months: Gitolite and GitWeb backups retirement

Server backups will be destroyed another 12 months later.

This is scheduled for June 2025. Backups have been scheduled for destruction for the end of July 2025.