Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • G gitlab-ce
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • nexedi
  • gitlab-ce
  • Repository

Switch branch/tag
  • gitlab-ce
  • scripts
  • gitaly-test-build
Find file BlameHistoryPermalink
  • Stan Hu's avatar
    Use Praefect instead of Gitaly in testing loop · 63973c00
    Stan Hu authored Dec 14, 2020
    In the test environment, we go through the trouble of spinning up Gitaly
    and Praefect, only to bypass Praefect entirely and go directly to the
    Gitaly socket. This renders the Praefect step useless and causes us to
    miss errors in proxying.
    
    To fix this, we now proxy all calls through Praefect and add a second
    Gitaly shard.
    
    This was discovered in
    https://gitlab.com/gitlab-org/gitaly/-/issues/3379.
    63973c00

Replace gitaly-test-build

Attach a file by drag & drop or click to upload


Cancel
GitLab will create a branch in your fork and start a merge request.
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7