GitLab Manage Stage, 7 Mar 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Walkthrough: Bitbucket Cloud Importer

Description

Haris Delalić from the Import Team reviews the current state of the Bitbucket Importer by doing a quick import from Bitbucket Cloud into GitLab.com.

Doc: https://docs.gitlab.com/ee/user/project/import/bitbucket.html

A

Hi everyone- I am harry salalik and I am the product manager for group import here at gitlab.

A

Today, I'm going to walk through an import from bitbucket cloud into gitlab to show the current user experience and note any opportunities for improvement.

A

Bitbucket is one of our most used importers right after github I'll start by logging into my bitbucket account to review my data before migration.

A

So over here in bitbucket, I have created a test project repository named it bb repo. I have added a couple of issues in here with some comments in them and a milestone assigned to each.

A

In addition to that, I have two pull requests, one that has already been merged and one that is still open, and I do have a couple of commits going on with these pull requests.

A

So this is pretty much the overview of my data set. I will now switch over to gitlab and initiate the import to get to project import in gitlab. I have to create a new project.

A

So when creating a new project, the choices are created from templates, create a blank project and one of the choices I'm looking for is really the project import.

A

I'm going to select bitbucket cloud and after providing my oauth credentials, I am presented with the one repository I have in bitbucket as a choice for import.

A

I will choose to import it into a group that I have created for this purpose named bb import and I'm gonna name. My project.

A

Bitbucket repo, just sort of see a different name on the import. So to start, I will hit the import button.

A

And, as I could tell in the status, it went from scheduling to importing to complete that was pretty fast as expected, because there's really not a lot of data, but I just wanted to see the process and the completeness of the importer.

A

I will use the convenient go to project link to take a look at the project that I've created so as uh requested the project was named bitbucket repo.

A

I see that I have three commits two branches um and the two files, so this pretty much feels about right, at least at a high level.

A

I will dig in deeper to take a look at a the issues.

A

And, as I can tell uh there are, these are the two issues that I had created in bitbucket and in bitbucket I was able to select the issue type, whether it was going to be enhancement or a bug, and I can tell now that that data has come across as labels, which is really nice.

A

I also see that the milestones have been migrated, so the 1.1 and 2.2 in the 2.0 milestones are available here. For me,.

A

So the one thing that I notice is missing like immediately is this screenshot that I had in this first issue?

A

I can see that the.

A

The markup contains the link to the bitbucket repository and the image, but that image has not had not been imported or migrated into gitlab.

A

It is just being directly linked from here and since I'm no longer uh in bitbucket repo, I have no access to that particular url.

A

um So it's definitely a something that um you should be aware of that if there are any images that are directly uploaded and not just linked from you know an internet, accessible url, those images will not come across.

A

Looking at the merge requests.

A

I can see the one that was merged and the one that's still open the merge request that was merged.

A

Seems to have the information that I had originally provided.

A

And it also seems that my comments were imported.

A

um And let's see the link to the issue, results seems to work out in this case.

A

But I wonder if it's just because um the issue numbers in gitlab were also just one and two the same as in bitbucket, and if this was uh any different. Would that have the have still worked.

A

So the internal links seem to work appropriately.

A

And again, looking at the merge request, I can see the commit and I can see the author of the commit, which is my external user, so the user has been matched and I can see that within gitlab. Now I have that external user that was using bitbucket having been matched to the gitlab user using the email address, because it is a common email address of community systems.

A

So and um so we've seen the milestones, we have seen the issues and we have seen the merge requests and commits. uh We have also seen the repository with the files and those are all there.

A

I'm also just going to very quickly take a look at the labels, and it looks like all the labels that were available in bitbucket have been imported here, even if some of them are not used by my issues.

A

So all in all, it seems like it worked pretty um at the import work pretty fast and uh it imported all the major objects that I expected to have.

A

So that really concludes my walkthrough through the bitbucket import experience.

A

Thank you very much for watching and please let me know if you have any feedback.