Skip to content

GitLab Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
testcases
testcases
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 704
    • Issues 704
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 0
    • Merge Requests 0
  • Requirements
    • Requirements
    • List
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.org
  • quality
  • testcasestestcases
  • Issues
  • #52

Closed
Open
Opened Nov 08, 2018 by Nick Thomas@nick.thomas🏖Maintainer

QA tests for pull and push mirroring over SSH

Per gitlab-org/gitaly!959 (diffs, comment 115392278)

Pull and push mirroring over SSH is currently very poorly tested in gitaly and gitlab-rails.

It would be good to have a couple of scenarios in gitlab-qa, for pull and push mirroring, using both password and SSH public-key authentication.

Pull mirroring is EE-only, push mirroring is getting SSH authentication in %11.5 or %11.6.

In these scenarios, we would:

  • Set up two projects. One has data, one does not.
  • Configure a pull (in the empty project) or push (in the with-data project) mirror in Project -> Settings -> Repository -> Mirroring
  • Trigger "sync now" in the same place
  • Wait for the with-data project's commits to appear in the empty project
Edited Nov 08, 2018 by Nick Thomas
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: gitlab-org/quality/testcases#52