<p>Using Azure Repos Git to store binary artifacts like a zip file can indeed be awkward and not the best use of a source control system. There are better ways to manage binary artifacts that allow for more flexible versioning and better storage management. Here are some alternatives you can consider:</p>
<ol>
<li>Artifactory by JFrog
JFrog Artifactory is a popular choice for storing binary artifacts and can support any versioning scheme you prefer, including MAJOR.MINOR.PATCH.HOTFIX. Artifactory integrates well with Azure DevOps, and you can use it to store your zip files. You can set up a service connection in Azure DevOps to Artifactory and then use this connection in your release pipeline to fetch the artifacts for deployment.</li>
</ol>
<p>Steps to Integrate:
Set up Artifactory: First, ensure you have Artifactory set up and accessible.
Upload Artifacts: Configure your process to upload the zip files to Artifactory, with the versioning scheme you need.
Create Service Connection in Azure DevOps: Go to your Azure DevOps project settings and set up a service connection to your Artifactory instance.
Use in Release Pipeline: In your Azure DevOps release pipeline, use the Artifactory service connection to download the specific artifact version you want to deploy.
2. Azure Blob Storage
If you don't require the full feature set of a dedicated artifact repository, you can use Azure Blob Storage to store your zip files. Azure Blob Storage is cost-effective and supports storing large files without any specific versioning constraints.</p>
<p>Steps to Use:
Upload to Blob Storage: Automate the upload of your zip files to a Blob Storage container, possibly with a versioning scheme in the file name or path.
Access in Azure DevOps: You can access these blobs in your release pipeline either by using Azure CLI tasks, PowerShell scripts, or custom tasks designed to interact with Azure Blob Storage.</p>

CC BY-SA 4.0
2024-03-07T16:29:22.853Z
2024-03-07T16:29:22.853Z
geeky_girl
<p>We've just started to use Azure DevOps platform and having some doubts regarding artifactory type for release pipeline.</p>
<p>Here's the situation: we get complete delivery in zip file from Dev team which is ready to be deployed to the target machines, which means that build pipeline is unnecessary here. Therefore, there's no <code>publish</code> step.</p>
<p>We tried to create feed and connect Universal Packages to it which wasn't right solution for us because it supports only Semantic versioning 2.0 (<code>MAJOR.MINOR.PATCH</code>), but we need to have <code>MAJOR.MINOR.PATCH.HOTFIX</code> versioning.</p>
<p>The only working solution was to push zip delivery to Azure Repos Git and add it as an artifact to the release pipeline which seems little bit awkward.</p>
<p>Is there any better way to solve this problem? Maybe something like creating service connection to Jfrog or something similar and keep our artifacts there?</p>
<p>Thanks in advance.</p>

<azure><azure-pipelines><release><azure-artifacts>
Best artifactory type for Azure release pipeline
i8z
# Best artifactory type for Azure release pipeline

(Asked by: username_0 on 2023-11-29)

We've just started to use Azure DevOps platform and having some doubts regarding artifactory type for release pipeline.

Here's the situation: we get complete delivery in zip file from Dev team which is ready to be deployed to the target machines, which means that build pipeline is unnecessary here. Therefore, there's no `publish` step.

We tried to create feed and connect Universal Packages to it which wasn't right solution for us because it supports only Semantic versioning 2.0 (`MAJOR.MINOR.PATCH`), but we need to have `MAJOR.MINOR.PATCH.HOTFIX` versioning.

The only working solution was to push zip delivery to Azure Repos Git and add it as an artifact to the release pipeline which seems little bit awkward.

Is there any better way to solve this problem? Maybe something like creating service connection to Jfrog or something similar and keep our artifacts there?

Thanks in advance.

**Tags:** azure, azure-pipelines, release, azure-artifacts


---

## 1 answers

### Answer by username_1 on 2024-03-07. Score: 0

Using Azure Repos Git to store binary artifacts like a zip file can indeed be awkward and not the best use of a source control system. There are better ways to manage binary artifacts that allow for more flexible versioning and better storage management. Here are some alternatives you can consider:

1. Artifactory by JFrog
   JFrog Artifactory is a popular choice for storing binary artifacts and can support any versioning scheme you prefer, including MAJOR.MINOR.PATCH.HOTFIX. Artifactory integrates well with Azure DevOps, and you can use it to store your zip files. You can set up a service connection in Azure DevOps to Artifactory and then use this connection in your release pipeline to fetch the artifacts for deployment.

Steps to Integrate:
Set up Artifactory: First, ensure you have Artifactory set up and accessible.
Upload Artifacts: Configure your process to upload the zip files to Artifactory, with the versioning scheme you need.
Create Service Connection in Azure DevOps: Go to your Azure DevOps project settings and set up a service connection to your Artifactory instance.
Use in Release Pipeline: In your Azure DevOps release pipeline, use the Artifactory service connection to download the specific artifact version you want to deploy.
2. Azure Blob Storage
If you don't require the full feature set of a dedicated artifact repository, you can use Azure Blob Storage to store your zip files. Azure Blob Storage is cost-effective and supports storing large files without any specific versioning constraints.

Steps to Use:
Upload to Blob Storage: Automate the upload of your zip files to a Blob Storage container, possibly with a versioning scheme in the file name or path.
Access in Azure DevOps: You can access these blobs in your release pipeline either by using Azure CLI tasks, PowerShell scripts, or custom tasks designed to interact with Azure Blob Storage.


---

