GitLab Manage Stage, 6 Mar 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Walkthrough: GitLab Group and Project Migration 14.8

Description

Haris Delalić from the Import Team reviews the current state of the GitLab Migration feature to import a Group including Subgroups and Projects from one instance of GitLab to another.

Feedback issue: https://gitlab.com/gitlab-org/gitlab/-/issues/284495

A

Hi everyone- this is harris dalalik and I am the product manager for the import group here at gitlab.

A

Today, I'm going to do a full review of a recently developed, gitlab feature that allows me to migrate a gitlab group, including all of the subgroups and projects from one instance of gitlab to another, using a single mouse click.

A

This is the group that I have created for this purpose. um I have added a couple of subgroups and projects within the tree so that we have a lot of different data to import.

A

To start the migration. I will select a new group.

A

And instead of creating a blank group, I will choose to import a group in order to import a group from another instance of gitlab. You have to provide the url and the personal access token for that instance, so, once I've provided that this page will connect that instance, it will look at all of the groups groups that I have access to and give me a list of everything that I am able to migrate.

A

So the group that I'm interested in migrating, of course, is my migration source group.

A

If you look at this view, you can actually tell that I had already imported that into a folder named migration test prior to this, so this will actually be a re-import of that same group. For me, in addition to that, this view also allows you to select a different name for the.

A

For the destination group you can select what group should this group be imported under or whether it should have no parent, which means it will end up being a top level group and finally, you're? Also, you also can select more than one of these to just take the import of multiple groups off. At the same time, if there were more than um 20 groups shown or more than 20 groups available uh you, you would see paging here and you'll be able to uh view it either 20 50 or 100 items per page.

A

So this view here scales well and allows you to show a lot more data than what I'm showing here right now, so to start off the import.

A

I will just hit this button here and, as we can tell, it goes uh into a pending state, which means that the migration is being scheduled, which then changes to importing, which means that migration is in progress.

A

I have done this um import before and it takes about four or five minutes to import the groups and the projects that I have, um while we're waiting for that import to complete I'd like to actually review the data that I have configured so that we would know sort of what to expect and be able to compare and make sure that everything that I had prior to the migration is also available afterwards.

A

So, as I said, I have several subgroups and projects each with a name, description and icon.

A

In addition to that, my overall top-level group has um has some settings that have flipped uh so we'll take a look at that. I have uh specifically disabled email, notifications and group mentions, and I expect those settings to also show up in the destination, and I had also added a badge in order to see if that gets migrated across.

A

So, um in addition to the groups, subgroups and projects, of course, I have added a lot of other different objects, for example labels here. So these are the group level labels that I had configured, and you will see that I have used these on my epics.

A

So if we take a look at the epics.

A

I've configured several epics and uh kind of nested them into a tree so that um I can see if that entire structure of epics is migrated correctly.

A

So taking a look at this one top level, epic that I have here within that epic, I have some markdown text an image. I have added a start date and an uh and a due date. I've had a label and.

A

Here's the structure of the sub-epics and the issues that I have here so you'll see that I have at least one closed issue. Some open issues and those issues have um labels, estimates and milestones associated with them.

A

So once the migration is completed, I will be coming back here and comparing each one of uh each one of these views and each one of these objects to what actually uh to the destination the migrated group in order to ensure that everything had been migrated across.

A

So, in addition to the issues, of course, I have some merge requests. I have, um let's see I've defined a board.

A

And milestones so, let's take a look at the board that I defined because that's the board. I expect to see um in the destination group when it's when the migration is completed.

A

And this is a local instance, so it is taking a little longer to load, especially when it's busy doing the migration.

A

So it seems like the milestones that I have configured are the 1.1 and the 2.0, and you can also see the issues and the merge requests associated with those.

A

As far as the boards go, hopefully we'll be able to see very soon that um I have configured a group board.

A

That I named group board.

A

And in addition to the standard open and closed um columns, I have added a column in the middle. That only shows me the uh issues that have the budget label associated with them.

A

So um back to the epic tree, if we also pick a sub epic.

A

I'd like to point out some of the elements of the sub epic that I expect to be migrated.

A

For this particular sub, epic, in addition to just the text in the markdown.

A

We do have again start date due date labels. Now there is a parent epic, so I expect this structure to be preserved.

A

And I also see that you know I do have some comments in.

B

A

And replies to the comments- and that is something like this conversation- is something I expect to see there as well and finally, all these events here so, for example, the fact that someone has changed the start date, someone has changed the due date or someone has added another epic as a parent epic, to this epic.

A

Those are all the things that I expect to uh see in a destination. I also see there is an uh a word emoji associated with.

A

With the epic itself and then there's a large image, so I expect this epic look exactly like this. When the migration is completed,.

A

So going back to the import status, I'm curious to see if the migration is done.

A

And given how slowly the page refreshed, uh I can definitely tell that the import is still running.

A

So, um finally, I wanted to also take a look at the project that is going to get migrated. So not only are we migrating the groups and subgroups, but we are now migrating all the projects that lie under that which includes the repository issues. Merge requests comments, all the things that projects have so this particular project.

A

I expect to be fully migrated when this is completed and all just all this was kicked off by clicking that one import button, so the groups, the subgroups and the projects will all come across as a structure via that one single button click, so just something that's noteworthy is that I do have some commits here, branches and and taking a look at the merge requests.

A

We can see some of the attributes of the merge requests that I would expect to see there.

A

So in particular, let's just open.

A

um This merge request here, which was created by a different user.

A

And it does reference.

A

Issue number two: I can see here that there were multiple events where um labels were added. Users were assigned, reviewers were assigned, and also here I can see that I've added a time estimate so time tracking is also something that I expect to see. Migrated.

A

um Quickly, checking this issue number two to see if I can uh see the reference to uh to the merge request from the issue.

A

That relationship is something that would be valuable to migrate as well.

A

So this is the issue that the merger quest is referencing.

A

And I'm not realizing that you know having a local instance and opening a lot of pages, while the migration is running, does take time and slows down both uh the responsiveness of the system overall, but also the um you know, it's gonna have the migration. Immigration is gonna just take longer because of this, so I'm slowing down the migration as well. um This is not something that you would typically see if you have an actual server running. This is just running all of uh off my laptop now.

A

So the issue is uh almost loaded. I expect in this uh area where it says, related, merge requests. I expect to see that merge requests that I was referencing uh listed here.

A

So, while that's loading, you should also note that this particular issue has a lot of different events. So here are the merge requests that are related, so two merge requests one for milestone, 1.1 one for milestone, 2.0.

A

um I see a lot of different events as well. All the things that were added edited added changed on the issue. I have the events for and now you know, I would expect all of those to also get migrated, and we can also see the time tracking on this issue as well.

A

So going back to the import status.

A

I will do another refresh.

A

Just make sure that this page did not get stale and that we get the latest status of the import.

A

And, yes, the import had completed.

A

And I can tell that.

A

This particular group has now been imported into the migration testing.

A

Group so opening up that um destination group to compare and see sort of how this migration, whether this migration was successful.

A

um First thing I notice is that the group migration seems to have completed so I have the group and the subgroups here.

A

However, it doesn't seem like the projects have been migrated, so you know I can see the epics here, but, for example, I see no issues and numbers requests.

A

B

Course I wonder if.

A

The projects just did not get migrated or whether the project migration, you know um background job, is still running, and this will still complete at some point, and I will then see uh the projects which include the issues repos and merger. Quests show up here.

A

I will now give this some time in order to complete and then come back to review kind of the success of this migration.

A

It turns out that there was a failure in migrating one of the projects, which is why the migration was not complete.

A

I was able to see that failure in the history and as I can tell there was a problem um with extracting the data from the project, so I will have to follow up and see what the issue is and how to correct that and we'll do another one of these videos once I am able to get past that so for now, um thank you for watching and have a great day.