Skip to content
Snippets Groups Projects

Repo import 4.1 fix (empty repositories)

Merged gitlab-qa-bot requested to merge github/fork/escaped/repo-import-4.1-fix into 4-1-stable

Created by: escaped

Fix for #2830 (closed) Includes fix from #2695

Import all repos to global namespace, otherwise the new generated repositories are empty!

Merge request reports

Loading
Loading

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
  • Created by: scross01

    I applied the fix to import to the global namespace, but also found that the import is creating a new (empty) git repository with different capitalization and replacing special characters. e.g.

    cp -R My.Project.git /home/git/repositories
    cd /home/git/gitlab
    bundle exec rake gitlab:import:repos RAILS_ENV=production

    After import the new (empty) repository is called /home/git/repositories/my-project.git

    Replacing the new repository with the original resolves the problem

    cd /home/git/repositories
    rm -Rf my-project.git
    mv My.Project.git my-project.git

    Or alternatively, copy the original into the repositories folder with the appropriate naming format before running the import

    cp -R My.Project.git /home/git/repositories/my-project.git
    cd /home/git/gitlab
    bundle exec rake gitlab:import:repos RAILS_ENV=production

    By Administrator on 2013-04-07T18:33:36 (imported from GitLab project)

    By Administrator on 2013-04-07T18:33:36 (imported from GitLab)

  • Created by: anibalpacheco

    I'm using master, the patch seems to be already aplied in master, but my repos are still beeing imported with no metadata nor files, only their names

    By Administrator on 2013-04-10T21:43:10 (imported from GitLab project)

    By Administrator on 2013-04-10T21:43:10 (imported from GitLab)

Please register or sign in to reply
Loading