Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • heptapod heptapod
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 161
    • Issues 161
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • heptapod
  • heptapodheptapod
  • Issues
  • #228

Closed
Open
Created Mar 27, 2020 by Georges Racinet@gracinet🦑Owner

Adaptations for repo migration to hashed storage

In Gitlab 12, repositories can be stored in a hierarchy with directory names that are hashes, but it's not systematic, especially for repositories predating the migration from Heptapod 0.8.

There's a rake task to migrate the repositories to the hashed storage. I don't expect it to work at all for Heptapod 0.12.0rc4. It must work in Heptapod 0.12.0

The hashed storage is the one used by default on GDK based development setups, and Heptapod 0.12.0 RCs work on it with only one problem, the group HGRC issue mentioned in the changelog.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking