Skip to content

GitLab Migration - Selective project migration

This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.

Summary

From this comment:

I don't know if we already have an issue for this, but regarding the concerns with reliability, I think a great feature would be for the user to be able to choose which objects would they like to migrate. This could help them if they don't care about some of the objects. For instance, optionally not migrating uploads could make the migration much faster/lighter. Also if they tried a migration once and failed for some specific object, they could then re-try the migration, this time unchecking the failed object.

From the UI, I imaging we would show them something like this before the migration is triggered:

  • Groups
    • Users
    • Labels
    • Epics
    • Projects
      • Repository
      • LFS
      • Labels
      • Issues
      • Merge Requests
      • File Uploads

[CONFIRM]

Related ideas

  • Option to limit date/age of objects for project migrations - See more info: #39168
  • Option to not migrate closed objects - See more info: #223129

Technical perspective

From a technical perspective, I think we could save these custom options in jsonb column in the bulk_imports table. Then, we'd read this column to decide whether we start/skip certain pipelines, similar to what we're going to do with the Project Version check.

I think this could be a backend-weight3, if I'm not missing anything . We also need to inform the FE with the possible objects.

Edited by 🤖 GitLab Bot 🤖
OSZAR »