ARTIFACTORY: Git client commands (git clone / fetch / pull / push) are not supported against a VCS remote repository

Products
Frog_Artifactory
Content Type
Administration_Platform
AuthorFullName__c
Jeremy Leopold
articleNumber
000007016
FirstPublishedDate
2026-06-23T13:32:29Z
lastModifiedDate
2026-06-23

ARTIFACTORY: Git client commands (git clone / fetch / pull / push) are not supported against a VCS remote repository

A VCS remote in Artifactory is an HTTP caching proxy for source archives — it is not a Git server. Pointing git clone, git fetch, git pull, or git push at any Artifactory URL will fail.

The same applies to any tool that calls a git binary under the hood, including:
  • SwiftPM
  • Cargo with git sources
  • npm git+https:// dependencies
  • pip install git+
  • Helm git sources
  • Go modules consumed by import path


What a VCS Remote Is

A VCS remote talks to the upstream Git provider (GitHub, GitLab, Bitbucket, etc.) over the provider's web and REST endpoints, then re-exposes the results — tarballs, zip archives, and JSON metadata — through Artifactory's own api/vcs/... REST surface.

It does not speak the Git wire protocol on either side beyond the minimum needed to enumerate refs.

From the JFrog blog post :
VCS remote repositories are designed to cache and proxy raw Git artifacts (like .zip archives of specific branches or tags) served over HTTP/HTTPS. They are not designed to emulate a full Git server. … Artifactory's VCS repository, while interacting with Git behind the scenes, presents these Git assets as files via HTTP. It does not provide the underlying Git protocol necessary for a native Git client's direct Git cloning mechanism.
The page title "VCS Repositories" and the documentation phrase "Artifactory can be configured to proxy Git repositories" both describe this archive-proxy behavior — proxying source archives served from Git providers, not proxying the Git wire protocol itself.

A git client expects to negotiate git-upload-pack or git-receive-pack over Smart HTTP or SSH; Artifactory implements neither.


Supported Operations (via api/vcs/...)

Operation

Endpoint

List branches

GET api/vcs/branches/<repo>/<org>/<name>

List tags

GET api/vcs/tags/<repo>/<org>/<name>

Download branch as archive

GET api/vcs/downloadBranch/<repo>/<org>/<name>/<branch>?ext=tar.gz

Download tag as archive

GET api/vcs/downloadTag/<repo>/<org>/<name>/<tag>?ext=tar.gz

Download commit as archive

GET api/vcs/downloadCommit/<repo>/<org>/<name>/<sha>?ext=tar.gz

Download release

GET api/vcs/downloadRelease/<repo>/<org>/<name>/<release>?ext=tar.gz

Download a single file from a branch

GET api/vcs/downloadBranchFile/<repo>/<org>/<name>/<branch>!<path>?ext=zip

Download a single file from a tag

GET api/vcs/downloadTagFile/<repo>/<org>/<name>/<tag>!<path>?ext=zip



Notes
  • ext defaults to tar.gz.
  • zip is also supported.
  • The single-file endpoints depend on the upstream provider exposing a raw-file URL. See the provider-specific knowledge base articles for GitHub, GitLab, and Bitbucket.


Reference