# Download Release Bundle

A release bundle groups together the contents that make up your release and provides the bill of materials for the release. For example, you can group together the different build artifacts, such as Docker images, that make up your release. The group of files can then be deployed as a single unit to your devices.                                                                                                                                                                                                                

A release bundle plays a central role in the distribution flow. It specifies the different files, packages, and metadata that comprise a release, and is created and managed in[ JFrog Distribution](https://www.jfrog.com/confluence/display/JFROG/JFrog+Distribution). Since all the files specified in a release bundle are required in order to keep the release coherent, a release bundle is immutable. 

JFrog Connect supports Release Bundles v1 and v2. 

## Download Release Bundle Action

The Download Release Bundle step type enables you to deploy a versioned package of software artifacts to your edge devices. In addition, a release bundle has the ability to deploy Docker images using the Docker Compose engine.                                                                                                                                   

## Prerequisites                                               

* Connect Agent 6.0 or later and at least one device registered.
* A release bundle that is ready for deployment.
* In the [Create Update Flow](https://docs.connect.jfrog.io/features-new-ui/deployments/update-flow) procedure, completed through Step 3.

## Add a Step and Configure the Step Type <a href="#add-a-step-and-configure-the-step-type" id="add-a-step-and-configure-the-step-type"></a>

To add a step and configure the step type you have chosen, do the following:

1. In the Create New Flow page, click **Add Step**.
2. In the **Step Type** dropdown list, choose **Download Release Bundle**, give the step a **Step** **Name**, and create the step. You can change the step name afterwards if you need to.
3. Choose the **JFrog Registry** where your release bundle is stored. If the registry does not appear in the list, go to [Add JFrog Registry](https://docs.connect.jfrog.io/administration-new-ui/general-settings/registry/add-jfrog-registry) to add yours to the list. Then return to this configuration and the added registry will appear in the list.

{% hint style="success" %}
**Tip**: If you want the step to pull content from an Artifactory Edge account, complete the procedure in [Add JFrog Registry](https://docs.connect.jfrog.io/administration-new-ui/general-settings/registry/add-jfrog-registry), and then choose that registry as your JFrog Registry.
{% endhint %}

<div align="left"><figure><img src="https://1679291640-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOX8HIrQ8f257lv49Od1Z%2Fuploads%2FCdRWKjyrtDisS9EoBsyS%2Fdownload-release-bundle-nui-01.png?alt=media&#x26;token=dd570f47-249b-44d6-afe8-0f125a0c532c" alt="" width="563"><figcaption></figcaption></figure></div>

4. Enter a **Name** for your release bundle and the **Version** of the release bundle that you used in Artifactory.

{% hint style="success" %}
**Tip**: If you need help finding the Name and Version in Artifactory, see [Get Artifactory Parameter for Release Bundle](https://docs.connect.jfrog.io/features-new-ui/deployments/update-flow/step-types/download-release-bundle/get-artifactory-parameters-for-release-bundle).

When you deploy the Download Release Bundle update flow with a v2 release bundle, Connect will automatically use the release bundle name and version as the deployment tag and version.
{% endhint %}

5. Enter the **Device Path**. This is where the release bundle will be installed on the edge devices. The directory on the device must exist beforehand, otherwise, the update will fail. Connect does not automatically create directories when deploying updates. You may create a folder using the Run Command step type.

## Extract Content (Optional)

1. **Docker Compose**: (Optional) If your release bundle includes Docker images, specify the **Release Bundle Path** and the **Device Path** for the Docker Compose YAML file.

<div align="left"><figure><img src="https://content.gitbook.com/content/OX8HIrQ8f257lv49Od1Z/blobs/QV6PCAROcBp1fYs965kf/download-release-bundle-nui-02.png" alt="" width="563"><figcaption></figcaption></figure></div>

{% hint style="success" %}
**Tip**: If you need help finding the Artifactory Path in Artifactory, see [Get Artifactory Path.](https://docs.connect.jfrog.io/features-new-ui/deployments/update-flow/step-types/download-artifacts/get-artifactory-path)
{% endhint %}

2. **Alternative Path**: (Optional) If you have one or more files in your release bundle that need to go to different paths on the edge device, click **Add**. Then specify the **Release Bundle Path** and the **Device Path** for each file.

<div align="left"><figure><img src="https://content.gitbook.com/content/OX8HIrQ8f257lv49Od1Z/blobs/kyAnhF5JXfHkniB411Jb/download-release-bundle-nui-03.png" alt="" width="563"><figcaption></figcaption></figure></div>

## On Failure (Optional)

1. Configure your [On Failure](https://docs.connect.jfrog.io/features-new-ui/deployments/update-flow/on-failure-and-rollback) policy and instructions for rolling back.&#x20;
2. Save your step configuration.

## What’s Next?

Learn more about [Update Parameters](https://docs.connect.jfrog.io/features-new-ui/deployments/update-flow/use-update-parameters) and find out how they might be useful for your Release Bundles flow.