GitLab Import Group, 16 Aug 2021

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: GitLab 14.3 Kickoff - Manage:Import

Description

Import 14.3 planning issue: https://gitlab.com/gitlab-org/manage/general-discussion/-/issues/17369

A

Hello and welcome to the 14.3 kick-off for group import.

A

I have in the audience hannah sutor, who is our product manager on access.

A

I will share the planning document so that we can all follow along.

A

So, for 14.3, group import has a pretty focused objective, and that is.

A

Delivering the project, migration- and here we're talking just about migrating empty projects.,.

A

With the delivery of the groups, migration, which was done in 14.2,,.

A

We are now able to start focusing on delivering the projects as part of groups.

A

Migration and the very first mvc we're gonna, try and deliver in 14.3 is just delivering a project.

A

Without any of the relationships that it has. so, the fact that there's a project, plus all the.

A

Attributes that normally come across is included in here,, but nothing else. so,. That is the only.

A

Issue that we're delivering that is related to our direction., the rest of 14.3. We will spend.

A

On infradev and security issues. we have an engineering allocation of 50% of our backend.

A

Engineering team that is allocated to infradev and security issues,, so we expect to be able to draw.

A

Down that backlog significantly by first starting with some of the top issues which are p1s and p2s.

A

And then we'll continue with this allocation until we get to the bottom of our security backlog.

A

So,, that is pretty much all that I have to share for 14.3. any questions from the audience?.

A

I was going to ask one thing. so,: whenever you're talking about migrating groups, how.

B

Do you reconcile the concept of a group in the software that the team team is exporting from to.

B

Gitlab, is there always a one-to-one or is there somewhere along the way where you have to map?.

A

-That's, a good question., this particular importer is a gitlab to gitlab importer so, in this case,.

A

We are mapping a gitlab instance to another gitlab instance, and this could be a self-managed to a.

A

Dot com, or vice versa, or between two self-managed instances. So there is a one-to-one mapping between.

A

The groups on one side and the other we do not have so to kind of to follow up on that,.

A

We do not have many other importers that actually have this kind of a mapping.

A

Typically, we would migrate projects and all the things that hang off of projects, but things.

A

Like groups, don't always map to something in another platform. for example, in github, we have.

A

Organizations and there's some we're looking at potentially mapping an organization to a group, but.

A

It only works in some cases, because organization is not exactly a group, and sometimes you have.

A

More than one group representing an organization, we need to figure out how to map there, but we are.

A

Looking at some possible third-party importers where group import would work, but for now it's.

A

Really just the gitlab to gitlab. okay., all right, gotcha. great question, though, because I.

A

No one's ever asked me that before and I feel like there's probably people who have wondered kind of.

A

How does the group migration work from some other platform to gitlab.

A

If there's no other questions,, that pretty much concludes the kickoff for 14.3 for group import.

A

Thank you all for watching and thanks hannah for your participation. yeah, thank you. bye.