Distributing Release Bundles v2

❗
RLM Deprecation
As of July 31, 2026, all feature development, patches, and security fixes for Release Lifecycle Management will end, except for critical security fixes. RLM End of Life is currently scheduled for January 31, 2028. For more information, see JFrog Release Lifecycle Management Deprecation - End of Life.

📘
Subscription Information
This feature is supported with the Enterprise+ license.

📘
Note
This section describes how to distribute Release Bundles v2. For instructions about distributing Release Bundles v1, see Distribute Release Bundles (v1).

After you create a Release Bundle v2 version and promote it through the stages of your SDLC as needed, you can use JFrog Distribution to distribute it to targets to which you have distribution privileges, for example Edge nodes.

You can distribute Release Bundle v2 versions using one of the following methods:

JFrog Distribution triggers the replication process from the source JFrog Artifactory to the Edge nodes. First, it replicates the Release Bundle information to each Edge node and then initiates the replication process in the source Artifactory. For more details, see The Distribution Flow.

Prerequisites

The signing key defined in Artifactory must be propagated to the Edge nodes. See Propagate Signing Keys.

⚠️
Warning
The signing key must be valid. The operation fails if the key has expired.

Artifactory and the Edge nodes can be connected using one of the following methods:
- Using Scoped Tokens (Pairing Tokens): The JFrog Platform scoped tokens function connects the source Artifactory and the Edge nodes. This is the default option used to connect the source and node. If you cannot upgrade your self-hosted instance, or need to continue using the Circle of Trust, see the next method.
- Circle of Trust: A circle of trust between your source Artifactory and the Edge nodes applies to both the source and target Artifactory nodes.

Prerequisites

Related Topics