Artifacts
The Artifacts action block enables you to deploy updates to your devices by specifying a path in JFrog Artifactory to a destination path on your device.
Overview
The Artifacts action block enables you to create a workflow that pulls artifacts from your Artifactory instance and deploys them to your edge devices. You can deploy one or multiple artifacts using a single action block.
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 Block
To include the Artifacts action block in your update flow, do the following:
Go to Updates in the left sidebar and click Create Update Flow.
Drag the Artifacts action block and drop it in the workflow.
Configure the Action Block
Click the action block to open and configure it.
Enter a name for the action block.
Choose the JFrog account where your artifacts are stored.
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.
If you want to deliver more than one file, click Add More. Add an additional row for each additional file to deliver.
Enter the Destination Path on Device. 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 block in the General Section.
Configure your On Failure policy and instructions for rolling back, if necessary.
Save your action block configuration.
On Failure and Rollback
For your On Failure policy, choose the actions for Connect to do in case the Git Repository action block fails.
Continue Update Flow: If the Git Repository action block fails, Connect will simply continue with the next action block in the update workflow.
Run General Rollback: The action block and the entire update workflow are rolled back.
Do Action: The action to do when this action block 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 Release Bundle.
Last updated
