Skip to content
GitLab
Next
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 44,761
    • Issues 44,761
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,330
    • Merge requests 1,330
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • 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
  • GitLab.orgGitLab.org
  • GitLabGitLab
  • Issues
  • #18993
Closed
Open
Issue created Aug 02, 2017 by Nick Thomas@nick.thomas🆓Contributor0 of 1 checklist item completed0/1 checklist item

Support scp-style URLs in pull and push mirroring

The following discussion from gitlab-ee!2551 should be addressed:

  • @DouweM started a discussion: (+4 comments)

    How hard would it be to support the git@gitlab.com:gitlab-org/gitlab-ee.git syntax too? I think that if we don't support that, we'll get a lot of support requests about "invalid URL" errors :)

We can transform the URL to be well-formed in the frontend or backend and store as ssh://..., or we can accept scp-style URLs and store them as-is.

The URLs end up being written to a .git/config file as we set up a remote for each mirror, so either approach would work.

Currently, attempts to use scp-style URLs give a 500 error and an exception message like: Addressable::URI::InvalidURIError: Invalid port number

Edited Nov 28, 2018 by Nick Thomas
Assignee
Assign to
Time tracking