Download Artifact

The Download Artifact action enables you to deploy updates to your devices by specifying a path in JFrog Artifactory to a destination path on your device.

The Download Artifact action enables you to create a workflow that pulls artifacts from your Artifactory instance and deploys them to your edge devices. You can one or multiple artifact actions in an update flow.

Deployments using Artifactory consider the checksums of the files delivered. Therefore, the devices will pull only the diffs when downloading updates to files.

Prerequisites

• JFrog Connect and JFrog Platform accounts. (You receive a JFrog Platform account automatically when you register for a JFrog Connect account.)

• Connect Agent 6.0 or later and at least one device registered.

• One or more files ready for deployment and stored in your Artifactory repository.

Drag the Action

To include the Download Artifact action in your update flow, do the following:

1. Go to Deployment in the left menu and click Create Update Flow.

2. Drag the Download Artifact action and drop it in the workflow.

Configure the Action

Click the action to open and configure it.

1. Enter a name for the action.

2. Choose the JFrog Registry where your artifact is stored. If the registry does not appear in the list, go to Add JFrog Registry to add yours to the list. Then return to this configuration and the added registry will appear in the list.

1. Enter the Artifactory Path, for example, generic-repo/1.0/file.txt. You can also make all or part of the path a parameter. For example, you could make the version folder a parameter: generic-repo/{{version}}/file.text. Then you enter the version value when the actual deployment is run.

Tip: If you need help finding the Artifactory Path in Artifactory, see Get Artifactory Path.

1. If you want to deliver more than one artifact, add a new action for each artifact.

2. Enter the Device Destination Path. 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 action in the General Section.

3. Configure your On Failure policy and instructions for rolling back, if necessary.

4. Save your action configuration.

Artifactory Edge

If you want the action to pull content from an Artifactory Edge account, complete the procedure in Add JFrog Registry, and then choose that registry as your JFrog Registry in Step 2 above.

On Failure and Rollback

For your On Failure policy, choose the actions for Connect to do in case the Download Artifacts action fails.

• Continue Update Flow: If the Download Artifacts action fails, Connect will simply continue with the next action in the update workflow.

• Run General Rollback: The action and the entire update workflow are rolled back.

• Do Action: The action to do when this action is rolled back. In this case, the action is to revert all files.

Revert all Files

As a general precaution, Connect Agent creates a backup of the relevant device folder in a temporary location. If a rollback is required, the agent restores the folder to its initial state.

Free Memory Requirement

In order to enable Rollback functionality, your device's free memory must be greater than the update size. To calculate the amount of free memory required, use the relationship below:

Free Memory Required > Current Folder Size + Update Size + 10MB

What’s Next?

Learn how to build a workflow using a Download Release Bundle.