When you deploy software to your fleet, you can maintain maximum control by deploying first on a test group and then on production groups. This page describes how to do that in JFrog Connect.
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.
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 Groups, as defined in Manage your Fleet, or they can be subsets consisting of devices that use Tags to identify them as test devices.
Production groups in a project range from one to numerous groups that segment the devices by location, product type, or some other attribute(s).
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.
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:
Go to Deployments in the left menu and to the Update Flows tab. Find the flow you created and click the cloud icon in the Deploy column.
In the New Deployment wizard, enter any deployment parameters that are required, and click Next.
Enter the new groups and any additional filters you need.
Set the same Deployment Tag and Version that you used in the previous deployment (e.g., the successful test deployment or a previous production deployment).
Enter a comment that will help you identify the deployment, and run the deployment.
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.
Note: The numbers presented above are for example purposes only, and do not constitute specific recommendations for your devices.
Learn more about creating groups of devices.
Last updated
Was this helpful?
Was this helpful?
