Important
This section describes how to create Release Bundles v1. For information about creating Release Bundles v2, which were introduced in Artifactory 7.63.2 as part of the JFrog Release Lifecycle Management Solution, see Create Release Bundles (v2).
JFrog Distribution enables creating and distributing Release Bundles from the Artifactory service. Each Release Bundle may only contain artifacts from a single Artifactory service.
To create a release bundle, Distribution runs queries against the JPD in order to retrieve the required artifact references and their properties. Fetching the artifacts is performed according to the security privileges of the user who made the request.
To prevent tampering with the Release Bundle, it is signed by JFrog Distribution using a GPG key. The same GPG key is then used by the Artifactory Edge to validate the Release Bundle before it is accepted.
 |
Note
A Release Bundle version can include up to 3,000 artifacts. This number is not limited by the product, but exceeding it is highly unrecommended.
Methods for Creating Release Bundles
There are two methods for creating Release Bundles v1:
Using the REST API
Through the JFrog Platform UI
In either case, you define the artifacts to be included in the Release Bundle through a set of queries you can define.
In the final stages of creating a Release Bundle v1 in the JFrog UI, you can opt to save the Release Bundle in the following modes:
Draft version: You can create a draft version that can be edited by clicking Create.
Signed version (Unmodifiable): You can skip the draft phase by clicking Create & Sign to sign and finalize the process without a draft phase.
To search for a specific Release Bundle by name or by the latest version, use the filter search
The total count for both Distributable and Received Release Bundles is also displayed in the UI
Prerequisites
Creating a Release Bundle requires the Release Bundle 'Write' permissions.
Note
When creating a Release Bundle, the artifact properties are fetched from the Properties in Deployment and Resolution into the Release Bundle. Additional custom properties can be added during the initial Release Bundle version created using the Create Release Bundle REST API. These properties are transferred over to the Edge Node as part of the distribution process.