What: Diffusion git hosting moving to GitLab [0][1] When: Tuesday 2022-09-06 between 15:00 - 23:00 UTC Why: Unblocking sunsetting work for Differential/Diffusion [2]
What you can do: If you have not logged into https://gitlab.wikimedia.org/ yet to attach your Developer account and look around, now would be a great time!
Toolforge tool maintainers can use Striker (https://toolsadmin.wikimedia.org/) to create git repositories for each of their tools. Today these git repositories are hosted by https://phabricator.wikimedia.org/diffusion/. Starting on 2022-09-06 new repositories will be hosted under https://gitlab.wikimedia.org/toolforge-repos instead.
We will also be migrating the 474 existing Striker created repositories from Diffusion to GitLab starting on Tuesday 2022-09-06. This process will involve making each existing Diffusion repository read-only, copying it to GitLab, and finally configuring the Diffusion repo to be a read-only mirror of the GitLab repo. We hope that this set of operations will be the least disruptive way to migrate the repositories to the new hosting platform.
For tool maintainers with git repos that are migrating who *do not* yet have their Developer account attached at https://gitlab.wikimedia.org/, GitLab will send an email invitation to join the new repo. Because of some quirks of the login process that we are using for our GitLab service, the link in this email needs to be used *after* you have attached your account in order to grant you access [3].
[0]: https://phabricator.wikimedia.org/T296893 [1]: https://phabricator.wikimedia.org/T315706 [2]: https://phabricator.wikimedia.org/T191182 [3]: https://phabricator.wikimedia.org/T313366#8203450
Bryan, on behalf of the Toolforge administrators
Hi Bryan,
Just wanted to say thank you (and the rest of the Toolforge team) for putting in the effort of migrating all the repositories.
Although migrating a repository isn't that complex, the effort to sit down and figure out /what need to be done/ is quite large as I'm not as active in the development space as I used to be. Knowing that everything gets migrated means I don't even have to think about it -- and I really appreciate that!
Cheers,
Merlijn
On 02/09/2022 00:26, Bryan Davis wrote:
What: Diffusion git hosting moving to GitLab [0][1] When: Tuesday 2022-09-06 between 15:00 - 23:00 UTC Why: Unblocking sunsetting work for Differential/Diffusion [2]
What you can do: If you have not logged into https://gitlab.wikimedia.org/ yet to attach your Developer account and look around, now would be a great time!
Toolforge tool maintainers can use Striker (https://toolsadmin.wikimedia.org/) to create git repositories for each of their tools. Today these git repositories are hosted by https://phabricator.wikimedia.org/diffusion/. Starting on 2022-09-06 new repositories will be hosted under https://gitlab.wikimedia.org/toolforge-repos instead.
We will also be migrating the 474 existing Striker created repositories from Diffusion to GitLab starting on Tuesday 2022-09-06. This process will involve making each existing Diffusion repository read-only, copying it to GitLab, and finally configuring the Diffusion repo to be a read-only mirror of the GitLab repo. We hope that this set of operations will be the least disruptive way to migrate the repositories to the new hosting platform.
For tool maintainers with git repos that are migrating who *do not* yet have their Developer account attached at https://gitlab.wikimedia.org/, GitLab will send an email invitation to join the new repo. Because of some quirks of the login process that we are using for our GitLab service, the link in this email needs to be used *after* you have attached your account in order to grant you access [3].
Bryan, on behalf of the Toolforge administrators
Bryan,
How will this affect diffusion repositories that are already configured to mirror a remote repository? For example, https://phabricator.wikimedia.org/source/tool-xtools/ https://phabricator.wikimedia.org/source/tool-xtools/ mirrors GitHub, which means there is no need for anything to be moved to GitLab.
Matthew Bowker User:Matthewrb
On Sep 1, 2022, at 4:26 PM, Bryan Davis bd808@wikimedia.org wrote:
What: Diffusion git hosting moving to GitLab [0][1] When: Tuesday 2022-09-06 between 15:00 - 23:00 UTC Why: Unblocking sunsetting work for Differential/Diffusion [2]
What you can do: If you have not logged into https://gitlab.wikimedia.org/ yet to attach your Developer account and look around, now would be a great time!
Toolforge tool maintainers can use Striker (https://toolsadmin.wikimedia.org/) to create git repositories for each of their tools. Today these git repositories are hosted by https://phabricator.wikimedia.org/diffusion/. Starting on 2022-09-06 new repositories will be hosted under https://gitlab.wikimedia.org/toolforge-repos instead.
We will also be migrating the 474 existing Striker created repositories from Diffusion to GitLab starting on Tuesday 2022-09-06. This process will involve making each existing Diffusion repository read-only, copying it to GitLab, and finally configuring the Diffusion repo to be a read-only mirror of the GitLab repo. We hope that this set of operations will be the least disruptive way to migrate the repositories to the new hosting platform.
For tool maintainers with git repos that are migrating who *do not* yet have their Developer account attached at https://gitlab.wikimedia.org/, GitLab will send an email invitation to join the new repo. Because of some quirks of the login process that we are using for our GitLab service, the link in this email needs to be used *after* you have attached your account in order to grant you access [3].
Bryan, on behalf of the Toolforge administrators
Bryan Davis Technical Engagement Wikimedia Foundation Principal Software Engineer Boise, ID USA [[m:User:BDavis_(WMF)]] irc: bd808 _______________________________________________ Cloud-announce mailing list -- cloud-announce@lists.wikimedia.org List information: https://lists.wikimedia.org/postorius/lists/cloud-announce.lists.wikimedia.o... _______________________________________________ Cloud mailing list -- cloud@lists.wikimedia.org List information: https://lists.wikimedia.org/postorius/lists/cloud.lists.wikimedia.org/
My 2 cents: Ideally, it would move from Github to Gitlab. It's super easy to import into Gitlab, just need to provide the Github URL and that's basically it.
On Tue, Sep 6, 2022 at 2:47 PM Matthew Bowker matthewrbowker.ml@gmail.com wrote:
Bryan,
How will this affect diffusion repositories that are already configured to mirror a remote repository? For example, https://phabricator.wikimedia.org/source/tool-xtools/ mirrors GitHub, which means there is no need for anything to be moved to GitLab.
Matthew Bowker User:Matthewrb
On Sep 1, 2022, at 4:26 PM, Bryan Davis bd808@wikimedia.org wrote:
What: Diffusion git hosting moving to GitLab [0][1] When: Tuesday 2022-09-06 between 15:00 - 23:00 UTC Why: Unblocking sunsetting work for Differential/Diffusion [2]
What you can do: If you have not logged into https://gitlab.wikimedia.org/ yet to attach your Developer account and look around, now would be a great time!
Toolforge tool maintainers can use Striker (https://toolsadmin.wikimedia.org/) to create git repositories for each of their tools. Today these git repositories are hosted by https://phabricator.wikimedia.org/diffusion/. Starting on 2022-09-06 new repositories will be hosted under https://gitlab.wikimedia.org/toolforge-repos instead.
We will also be migrating the 474 existing Striker created repositories from Diffusion to GitLab starting on Tuesday 2022-09-06. This process will involve making each existing Diffusion repository read-only, copying it to GitLab, and finally configuring the Diffusion repo to be a read-only mirror of the GitLab repo. We hope that this set of operations will be the least disruptive way to migrate the repositories to the new hosting platform.
For tool maintainers with git repos that are migrating who *do not* yet have their Developer account attached at https://gitlab.wikimedia.org/, GitLab will send an email invitation to join the new repo. Because of some quirks of the login process that we are using for our GitLab service, the link in this email needs to be used *after* you have attached your account in order to grant you access [3].
Bryan, on behalf of the Toolforge administrators
Bryan Davis Technical Engagement Wikimedia Foundation Principal Software Engineer Boise, ID USA [[m:User:BDavis_(WMF)]] irc: bd808 _______________________________________________ Cloud-announce mailing list -- cloud-announce@lists.wikimedia.org List information: https://lists.wikimedia.org/postorius/lists/cloud-announce.lists.wikimedia.o... _______________________________________________ Cloud mailing list -- cloud@lists.wikimedia.org List information: https://lists.wikimedia.org/postorius/lists/cloud.lists.wikimedia.org/
Cloud mailing list -- cloud@lists.wikimedia.org List information: https://lists.wikimedia.org/postorius/lists/cloud.lists.wikimedia.org/
I also want to say thanks to Bryan for doing this. We are looking forward to retire the git-ssh service to reduce complexity when migrating Phabricator servers and generally reduce the number of different places we use for repos at Wikimedia.
On Tue, Sep 6, 2022 at 3:47 PM Matthew Bowker matthewrbowker.ml@gmail.com wrote:
Bryan,
How will this affect diffusion repositories that are already configured to mirror a remote repository? For example, https://phabricator.wikimedia.org/source/tool-xtools/ mirrors GitHub, which means there is no need for anything to be moved to GitLab.
This is a great question Matthew. I honestly had not thought about the possibility of any of these repos already being read-only mirrors of another repo. It should be possible for me to add some detection code to notice when a Diffusion repo has an "observe" URI attached to it.
I think we will just have to skip migration for this type of repo and remove Striker's knowledge of it. GitLab does not currently have a solution for actively mirroring from another git repo [0] that would allow us to make things go github->gitlab->diffusion at this point. I have already removed some of the code from Striker that would be needed to keep tracking both Diffusion and GitLab repos in the long term, so dropping this tracking is about all I can do for the xtools repo and any others setup similarly.
[0]: https://phabricator.wikimedia.org/T305984#8210132
Bryan
On Thu, Sep 1, 2022 at 4:26 PM Bryan Davis bd808@wikimedia.org wrote:
What: Diffusion git hosting moving to GitLab [0][1] When: Tuesday 2022-09-06 between 15:00 - 23:00 UTC Why: Unblocking sunsetting work for Differential/Diffusion [2]
What you can do: If you have not logged into https://gitlab.wikimedia.org/ yet to attach your Developer account and look around, now would be a great time!
Toolforge tool maintainers can use Striker (https://toolsadmin.wikimedia.org/) to create git repositories for each of their tools. Today these git repositories are hosted by https://phabricator.wikimedia.org/diffusion/. Starting on 2022-09-06 new repositories will be hosted under https://gitlab.wikimedia.org/toolforge-repos instead.
We will also be migrating the 474 existing Striker created repositories from Diffusion to GitLab starting on Tuesday 2022-09-06. This process will involve making each existing Diffusion repository read-only, copying it to GitLab, and finally configuring the Diffusion repo to be a read-only mirror of the GitLab repo. We hope that this set of operations will be the least disruptive way to migrate the repositories to the new hosting platform.
For tool maintainers with git repos that are migrating who *do not* yet have their Developer account attached at https://gitlab.wikimedia.org/, GitLab will send an email invitation to join the new repo. Because of some quirks of the login process that we are using for our GitLab service, the link in this email needs to be used *after* you have attached your account in order to grant you access [3].
The application has been updated to create new git repositories at https://gitlab.wikimedia.org instead of in Phabricator. A few bugs have been found in the migration process for the now legacy Diffusion repos. I will continue to work through these issues during my work day tomorrow.
NOTE: the "Git repositories" section of a tool's information in Striker now only displays GitHub hosted repositories. Do not panic if you look at a detail screen like https://toolsadmin.wikimedia.org/tools/id/replag and a Diffusion repo is no longer listed. We still have record of the Diffusion repos in the database. The GitLab replacement will show up as soon as it has been migrated.
Bryan
On Tue, Sep 6, 2022 at 4:38 PM Bryan Davis bd808@wikimedia.org wrote:
On Thu, Sep 1, 2022 at 4:26 PM Bryan Davis bd808@wikimedia.org wrote:
What: Diffusion git hosting moving to GitLab [0][1] When: Tuesday 2022-09-06 between 15:00 - 23:00 UTC Why: Unblocking sunsetting work for Differential/Diffusion [2]
What you can do: If you have not logged into https://gitlab.wikimedia.org/ yet to attach your Developer account and look around, now would be a great time!
Toolforge tool maintainers can use Striker (https://toolsadmin.wikimedia.org/) to create git repositories for each of their tools. Today these git repositories are hosted by https://phabricator.wikimedia.org/diffusion/. Starting on 2022-09-06 new repositories will be hosted under https://gitlab.wikimedia.org/toolforge-repos instead.
We will also be migrating the 474 existing Striker created repositories from Diffusion to GitLab starting on Tuesday 2022-09-06. This process will involve making each existing Diffusion repository read-only, copying it to GitLab, and finally configuring the Diffusion repo to be a read-only mirror of the GitLab repo. We hope that this set of operations will be the least disruptive way to migrate the repositories to the new hosting platform.
For tool maintainers with git repos that are migrating who *do not* yet have their Developer account attached at https://gitlab.wikimedia.org/, GitLab will send an email invitation to join the new repo. Because of some quirks of the login process that we are using for our GitLab service, the link in this email needs to be used *after* you have attached your account in order to grant you access [3].
The application has been updated to create new git repositories at https://gitlab.wikimedia.org instead of in Phabricator. A few bugs have been found in the migration process for the now legacy Diffusion repos. I will continue to work through these issues during my work day tomorrow.
NOTE: the "Git repositories" section of a tool's information in Striker now only displays GitHub hosted repositories. Do not panic if you look at a detail screen like https://toolsadmin.wikimedia.org/tools/id/replag and a Diffusion repo is no longer listed. We still have record of the Diffusion repos in the database. The GitLab replacement will show up as soon as it has been migrated.
Migration of the existing Diffusion repositories to GitLab is now complete. In the end 347 of the original 474 repositories were migrated. The other 127 repositories were in some way invalid for migration. See comments in https://phabricator.wikimedia.org/T315706 if you are interested in the details.
Bryan