JFrog Connect
HomePricingDashboardRegister Now
Search…
JFrog Connect
OVERVIEW
Architecture
Getting Started
JFrog Platform
Register
Register a device
Registering devices at scale
Registering Yocto image
Create Update
Update Flow
Integrations
Upload Files
Deploy Files
Deploy Container
Git Repository
Artifacts
Release Bundle
Create Update Parameters
Rollback
Update Devices
Update Deployment
Applications
Deployment Best Practice
Device Registration & Deployment
Schedule Update
Deploy Update Parameters
Devices
Filter bar
Map / Location
Delete a device
Control Center
Remote control
Remote access
Remote commands
Monitor
Resources monitor
Processes monitor
Data monitor
Alerts
Overview
Webhook
Fetch
Fetch logs
Device security
Active
REST API
Overview
Device state
Bulk devices state
Get devices details
Change devices details
Data monitor
Deploy Update
Update Trigger
Tags
Apps
Environment
Environment variables
Running Commands as User
SETTINGS
Account
User management
Notifications
Security
Troubleshooting
Device registration
Display issue - "0.0"
Micro update
Remote control
FAQ
GENERAL TERMS OF SERVICE
Frequent questions
Service-Level Agreement
Billing
Deprecated
Deprecated OTA updates tools
Micro updates
Container updates
Deprecated REST API endpoints
Non-Linux Agent
Powered By GitBook
Deprecated OTA updates tools
JFrog Connect provides 2 options for deploying OTA updates on remote Linux based devices.

Over-the-air software updates tools

  1. 1.
    Micro updates - Micro updates are application updates. You can update your application's code, install new packages, and run bash commands before/after the update is deployed. Usually, you would use a Micro update to deploy a new release of your application or patch a bug on your entire fleet of devices.
  2. 2.
    Container updates - Container updates are updates for containers. You can deploy a new release of your container on your entire fleet of devices. Currently, container updates are available only for Docker repository containers (contact us for different repositories).
​

Deployment best practice

To deploy an OTA update in a stable reliable way, make sure to have a few groups that are separated to: Test group - devices that are in your development lab and are similar to the devices that are in production. Production groups - from one to unlimited groups that include the deployed devices by location, product type, etc.
Update deployment best method: First, deploy the OTA update on the Test group, make sure that everything worked as expected, and your lab devices running in the way they should after the software deployment you did.
Then, Deploy the same update on the needed production group by going to the 'Recent updates' tab under the 'Updates' category, clicking on the 'Deploy to others' button and choosing the relevant production group to begin the deployment on.
​

Connect OTA update methodology

By default, updates are being deployed in the order they were sent. In case the device is offline by the time the update was sent, the updates will roll out in the right order when the device gets back online.
​
​
Previous
Subscription Service Agreement
Next
Micro updates
Last modified 2mo ago
Copy link
Outline
Over-the-air software updates tools
Deployment best practice
Connect OTA update methodology