Skip to content

Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Support
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
  • Sign in / Register
gitlab-runner
gitlab-runner
  • Project
    • Project
    • Details
    • Activity
    • Releases
    • Cycle Analytics
    • Insights
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
    • Locked Files
  • Issues 1,319
    • Issues 1,319
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 184
    • Merge Requests 184
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Security & Compliance
    • Security & Compliance
    • Dependency List
  • Packages
    • Packages
    • Container Registry
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • GitLab.org
  • gitlab-runnergitlab-runner
  • Issues
  • #4069

Closed
Open
Opened Mar 20, 2019 by Steve Azzopardi@steveazz
  • Report abuse
  • New issue
Report abuse New issue

Remove support for old clone/fetch methods

Description

GitLab Runner now requires Refspec information in the job response to clone the project which is sent from a GitLab instance that is running version %11.9+

Proposal

Remove the old code which used to clone and fetch the repository

Links to related issues and merge requests / references

Main deprecation issue #3473 (closed) MR introducing new clone/fetch method !1203 (merged)

Edited May 24, 2019 by Steve Azzopardi

Related issues

  • Discussion
  • Designs
Assignee
Assign to
12.0
Milestone
12.0
Assign milestone
Time tracking
None
Due date
None
5
Labels
Category:Runner Deliverable Verify [DEPRECATED] deprecation devops::verify
Assign labels
  • View project labels
Reference: gitlab-org/gitlab-runner#4069