You can use the Builds table to create a Release Bundle v2 from one or more builds, as an alternative to using the Release Lifecycle UI.
The procedures are described in the following sections:
Note
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 Projects is selected from the project selector).
Create a Release Bundle v2 from One or More Builds
Perform the procedure below to create a Release Bundle v2 from one or more builds.
To create a Release Bundle v2 from one or more builds:
In the Platform module, select Artifactory > Builds.
Click Create Release Bundle.
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.
Note
Naming restrictions:
The name is limited to 128 characters (see Tip below).
The version is limited to 32 characters (see Tip below).
The name and version must begin with a letter, digit, or underscore.
The name must consist only of letters, digits, underscores, periods, and hyphens. The version supports these characters and also supports the plus sign (+).
[optional] Select a signing key. If you do not select a key, a default key (generated by Artifactory automatically) is used. See Create Signing Keys for Release Bundles (v2).
Warning
Make sure the signing key is valid. The operation will fail if the key has expired.
Click Next to move to the Builds Selection tab.
Define the builds from which to create the Release Bundle:
Select the name and version of the build from the lists provided.
[optional] Select the Include Build Dependencies checkbox to have the Release Bundle include the dependencies associated with the build.
Important
Dependencies located in local, Federated, and remote repositories can be included in the Release Bundle. To include dependencies from a remote repository, you must first ensure that they exist in the remote cache. If they are not in the cache, you need to download them before creating the Release Bundle.
Click Add. The selected build and version appear in the selection box.
Click Create. The Release Bundle appears:
On the stages board.
As an event in the Release Bundle version timeline.
In the Release Bundle column of the Builds table.
Create a Release Bundle v2 from a Single Build
Perform the procedure below to create a Release Bundle v2 from a single, selected build.
In the Platform module, select Artifactory > Builds.
Click the name of the desired build, and then select Create Release Bundle from the actions menu.
Tip
Alternatively, click the name of a specific Release Bundle version and then click Create Release Bundle.
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.
Note
Naming restrictions:
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 must consist only of letters, digits, underscores, periods, and hyphens. The version supports these characters and also supports the plus sign (+).
[optional] Select a signing key. If you do not select a key, a default key (generated by Artifactory automatically) is used. See Create Signing Keys for Release Bundles (v2).
Click Next.
In the Contents tab, review the list of modules (containing artifacts and dependencies) to be included in the Release Bundle.
(optional) Select the Include Build Dependencies checkbox to have the Release Bundle include the dependencies associated with the build.
Important
Dependencies located in local, Federated, and remote repositories can be included in the Release Bundle. To include dependencies from a remote repository, you must first ensure that they exist in the remote cache. If they are not in the cache, you need to download them before creating the Release Bundle.
Click Create. The Release Bundle appears:
On the stages board.
As an event in the Release Bundle version timeline.
In the Release Bundle column of the Builds table.