Skip to content
GitLab
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
    Projects Groups Topics Snippets
  • Register
  • Sign in
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 9,362
    • Issues 9,362
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Jira
    • Jira
  • Merge requests 139
    • Merge requests 139
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar

Do not update/delete: Banner broadcast message test data

Do not update/delete: Notification broadcast message test data

  • GitLab.orgGitLab.org
  • GitLabGitLab
  • Issues
  • #3118
Closed
Open
Issue created Aug 08, 2017 by Stan Hu@stanhuMaintainer

Implement migration path from legacy to hash-bashed storage format

With https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/13246, we are going to need to find a way to migrate projects from the legacy (e.g. project name) to the hash-based (important: no longer UUID) storage format.

To start, I think we'll want:

  • Add some way for the admin to see how many projects/which projects are using the legacy format
  • Add a way for the admin to migrate in bulk (e.g. API, Rake task, etc.)

Ideally, we'd be able to kick this migration process off for GitLab.com and have it complete over some time. We should be able to halt things if necessary.

Should we consider making this a requirement in 10.0 for Geo-replicated repositories?

/cc: @brodock, @pcarranza, @DouweM

Edited Sep 08, 2017 by Gabriel Mazetto
Assignee
Assign to
Time tracking