Artifactory can be configured to proxy Git repositories by creating a Generic remote repository and pointing it to the Git provider's URL. The configuration is handled by setting the remote repository's URL to the git provider's URL, such as https://github.com or a self-hosted Git server URL. Artifactory supports proxying the following Git providers, as displayed below:
Use the custom provider if you have a Git repository that does not exist in the pre-defined list. In this case, you need to provide Artifactory with the download paths for your Git tarballs.
You do so by providing 4 placeholders:
Placeholder | Description |
|---|---|
{0} | Identifies the username or organization name. |
{1} | Identifies the repository name. |
{2} | Identifies the branch or tag name. |
{3} | Identifies the file extension to download. |
This placeholder system is designed for a simple owner/repository path. It does not support additional path segments, meaning nested repository structures like GitLab's group/subgroup/repository are incompatible.
For example, GitHub exposes tarball downloads at: https://github.com/<user>/<repo>/archive/<tag/branch>.<extension>
Therefore, the custom download path configured for Artifactory should be {0}/{1}/archive/{2}.{3}