Skip to content
GitLab Next
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • gitlab-runner gitlab-runner
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 2,478
    • Issues 2,478
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 123
    • Merge requests 123
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.orgGitLab.org
  • gitlab-runnergitlab-runner
  • Issues
  • #4600
Closed
Open
Created Aug 09, 2019 by Anton Maklakov@antmak

Use clone strategy if fetching got error

Summary

I use fetch strategy for my 1GB source project. Sometimes contents of .git/ directory gets corruption (probably because previous pipeline was canceled, i think). Because of that, code fetching finishes with error. Any other retries to make the same result ( .git/ directory is still corrupted ).

Expected behavior

I wish if the fetching stage is finished with error, gitlab-runner would keep going with clone strategy.

Used GitLab Runner version

11.11.2

Assignee
Assign to
Time tracking