In the Application module, go to Artifactory > Builds.
Click the name of the build to be used to create the Release Bundle.
From the actions menu on the right, select Create Release Bundle.
If the Release Bundle is created from a build associated with a project, the Release Bundle will also be associated with the project, even when working in a global context (i.e. when All is selected from the project selector).
In the Release Bundle Details tab of the New Release Bundle window, do the following:
Enter a name for the Release Bundle. (If a Release Bundle was previously created from the selected build, its name will appear.)
Enter the version number of the Release Bundle.
The name is limited to 128 characters.
The version is limited to 32 characters.
The name and version must begin with a letter, digit, or underscore.
The name and version must consist only of letters, digits, underscores, periods, and hyphens.
Select a signing key.
In the Contents tab, review the list of modules (containing artifacts and dependencies) to be included in the Release Bundle:
If the build contains a manifest, the contents of the Release Bundle will be based on the manifest. Using a manifest ensures that only those files that are meant to reach production are included in the Release Bundle. For more information, see Release Bundle Manifest for Builds.
If the build does not contain a manifest, the entire contents of the build artifacts will be included. This might include supporting files that are used during development but are not part of the final product.
In the current version, you cannot modify the list of contents in the UI. To modify the contents of the Release Bundle, you need to create a new manifest or use the APIs to create the Release Bundle. The property key of the manifest must be
(optional) Select the Include Build Dependencies checkbox to have the Release Bundle include the dependencies associated with the build.
Dependencies must be located in local or Federated repositories to be included in the Release Bundle. Dependencies located in remote repositories are not supported.