Skip to content
GitLab
Next
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • GitLab FOSS GitLab FOSS
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1
    • Merge requests 1
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.orgGitLab.org
  • GitLab FOSSGitLab FOSS
  • Issues
  • #41776
Closed
Open
Issue created Jan 08, 2018 by Nick Thomas@nick.thomas🆓Contributor

Migration to store project full path in repository

In https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/16027#note_53728095 we added a new configuration item to GitLab-managed git repositories, storing the project name as part of the configuration.

In the hashed storage case, this allows us to determine the namespace and project we should import a repository as, as part of a last-ditch "restore from this backup of /var/lib/git/repositories that I have" case.

However, existing installations won't get the new configuration item written unless they are migrated or transferred at some point. To be sure we can rely on this being present, we should consider having a rake task or background migration (latter preferred) to create this configuration item once, for all repositories.

I don't consider it very high-priority - it's only an issue if we're importing hashed storage repos, and when repos are migrated to hashed storage, the configuration will be written. So this only affects repos migrated between %10.0 and %10.3. Still, it's a bit of technical debt that I think is worth clearing up at some stage.

Assignee
Assign to
Time tracking