When managing an application fleet, you may require devices to be running different releases. By default, applications follow a rolling release policy where new releases are deployed to all devices in the fleet once successfully built. However, you can customize this behavior, so the application fleet or individual devices remain on a fixed release by pinning them.
Note: It is currently not possible to specify the application or device release policy via the balena CLI.
Pin application to a release
In the Applications dashboard, there is a Release policy header. By default, this policy is set to
track latest, which means that new releases are immediately deployed to all devices in the application when built. Expanding this Release policy dropdown menu displays all releases for the application, and you can select a specific release to pin the application to. When the application is pinned, all devices are updated to run the pinned release, and in the future, releases will not be deployed until the Release policy is updated to a newer release or set to
Pin device to a release
As well as pinning an application to a specific release, you may pin individual devices to a specific release. By default, all devices track the application release. However, you may wish to run a different release on select devices, for example, a development device or when performing a canary deployment.
To do so, from the Device dashboard, select the device menu and choose Pin to release.
Selecting Pin to release opens a modal window displaying a list of all successful application releases from which you can select a specific release to pin the device to.
Once the device has updated, it is shown to be on a Pinned release policy on the Application dashboard rather than following the release policy of the application.
You can also pin multiple devices to a target release in the Application dashboard by selecting them and choosing the Pin to release option from the Actions menu. Again this action opens a modal window allowing you to choose a specific release to pin the devices to.
Note: For more details about using the API to manage the release policy see the Fleet Management Masterclass.