LogoLogo
What's New?Connect Agent ReleasesBook a DemoPricing
  • Documentation
  • Developers
  • Administration
  • OVERVIEW
    • JFrog Connect Overview
      • Architecture Overview
        • Connect Agent
        • Connect & JFrog Platform
      • Plan Your Update Strategy
        • Software Update Objectives & Concepts
        • Software Update Process & Procedures
  • Get Started
    • Create JFrog Connect Account
    • Log in to JFrog Connect
    • Network Requirements
    • Register Device
  • Manage your Fleet
    • Register Devices at Scale
      • Freeze Image on Device
      • Build Image with Agent
    • Register & Update Device at Once
    • Organize Your Fleet
      • Create Project
      • Move Device between Projects
      • Create Groups
        • Add Device to Group
        • Add Many Devices to Group
        • Change Group Name
        • Delete Group
      • Tag Devices
        • Remove a Tag
      • Remove Many Devices
  • Devices
    • Fleet Overview
      • Filter Devices
      • Locate Devices
    • Device Details
      • Delete a Device
      • Block Updates with Update Trigger
    • Update Connect Agent
    • Delete Many Devices
  • Deployment
    • Create Update Flow
      • Actions
        • Run Command
        • Run Script
        • Deploy File
        • Deploy Docker
          • Use Docker Image
          • Use Docker Compose
          • Get Artifactory Parameters
        • Clone Git Repository
        • Download Artifact
          • Get Artifactory Path
        • Download Release Bundle
          • Get Artifactory Parameters for Release Bundle
        • Update Image
        • Install Debian Package
          • Get Artifactory Parameters for Debian
      • Use Update Parameters
      • On Failure & Rollback
      • Vulnerability Scans
      • Sample Use Case: Build Update Flow for Reuse
    • Deploy Software
      • Set Application & Version
      • Set Alert upon Failure
      • Set Phased Rollout
      • View Deployment Progress
        • Detailed Deployment Information
        • Abort a Deployment
      • Deploy in Groups
      • Sample Use Case: Deploy Docker Images to Devices
  • Tools
    • Remote Tools
      • Use Terminal
      • Open Port Tunnel Session
        • Access with VNC
        • Connect with SSH
        • Access Device Web Applications
      • Run Commands Remotely
        • Run Command as Non-Root User
      • Get Device Files (Fetch Files)
    • Alerts
      • Create Channel
      • Set Webhook
    • Monitor
      • Resource Monitor
      • Process Monitor
  • Releases
    • What's New?
    • Connect Agent Release Notes
  • Troubleshooting
    • Connect Server Status
    • Troubleshoot Topics
      • Device Registration
      • Display issue - "0.0"
      • Micro update
      • Remote control
Powered by GitBook
On this page
  • Test Groups
  • Production Groups
  • Method
  • Stage 1: Deploy on Test Groups and Validate
  • Stage 2: Deploy on Production Groups
  • Use Phased Deployments
  • What’s Next?

Was this helpful?

Export as PDF
  1. Deployment
  2. Deploy Software

Deploy in Groups

When you deploy software to your fleet, you can maintain maximum control by running your deployment on a test group and then on production groups. This page describes how to do that in JFrog Connect.

PreviousAbort a DeploymentNextSample Use Case: Deploy Docker Images to Devices

Last updated 5 months ago

Was this helpful?

When you deploy a software update to your edge devices, you want everything to go as smoothly as possible. If there are issues, the troubleshooting should be easy, and the number of devices impacted should be as low as possible. You can achieve this by deploying in groups.

Test Groups

To deploy a software update, you should start with one or more test groups. A test group includes devices that are in your development lab and are similar to the devices that are in production. Your test groups can be actual , as defined in , or they can be subsets consisting of devices that use to identify them as test devices.

Production Groups

Production groups in a project range from one to numerous groups that segment the edge devices by location, product type, or some other attribute(s).

Method

Stage 1: Deploy on Test Groups and Validate

Deploy the software update to one or more test groups. Ensure that everything is working as expected and that your test devices are running as expected. If there were issues, you may need to create a new deployment and test again before deploying to production groups.

Stage 2: Deploy on Production Groups

Once your software update has been validated using the test groups, you can use the same update flow on your production groups. To deploy the same software and update flow that you have previously deployed, do the following:

  1. Go to Deployment in the left menu and click Update Flows. Find the flow you deployed and click New Deployment.

  1. Click Select Devices and enter the new groups and any additional filters you need.

  1. Set the same Application and Version that you used in the previous deployment (e.g., the successful test deployment or a previous production deployment).

  1. Enter any deployment parameters that are required, and create the deployment.

Use Phased Deployments

Note: The numbers presented above are for example purposes only, and do not constitute specific recommendations for your devices.

What’s Next?

We recommend grading the deployments to your production groups by quantity of devices. For example, first deploy to two devices, then 20 devices, then 200 devices, and then continue to deploy groups in quantities that you feel comfortable with. As long as the deployments are successful and the updated software is working, you can re-use the same update workflow, changing only the destination groups (and/or filters) for each deployment phase. You can use the feature to create your phased deployments.

Learn more about of devices.

Phased Rollout
creating groups
Manage your Fleet
Groups
Tags