Create a Release Bundle (v2) from the Builds Table

JFrog Artifactory Documentation
Products
JFrog Artifactory
Content Type
User Guide
ft:sourceType
Paligo

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 dashboard.Create a Release Bundle (v2) from One or More Builds

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 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:

  1. In the Application module, select Artifactory > Builds.

  2. Click Create Release Bundle.

    RBv2_Build-screen_create-rb-button.png

  3. In the Release Bundle Details tab of the New Release Bundle window, do the following:

    1. Enter a name for the Release Bundle. (If a Release Bundle was previously created from the selected build, its name will appear.)

    2. Enter the version number of the Release Bundle.

      Note

      Naming restrictions:

      • The name is limited to 32 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.

    3. [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.

  4. Click Next to move to the Builds Selection tab.

  5. Define the builds from which to create the Release Bundle:

    1. Select the name and version of the build from the lists provided.

    2. [optional] Select the Include Build Dependencies checkbox to have the Release Bundle include the dependencies associated with the build.

      Important

      Dependencies must be located in local or Federated repositories to be included in the Release Bundle. Dependencies located in remote repositories are not supported.

    3. Click Add. The selected build and version appear in the selection box.

      create_RB_from_builds_dbox.png

  6. (optional) Select the Include Build Dependencies checkbox to have the Release Bundle include the dependencies associated with the build.

    Important

    Dependencies must be located in local or Federated repositories to be included in the Release Bundle. Dependencies located in remote repositories are not supported.

  7. Click Create. The Release Bundle appears on the kanban board and as an event in the Release Bundle version timeline.

Note

To exclude selected artifacts in the build from the Release Bundle, see Exclude Artifacts from a Release Bundle (v2).

Create a Release Bundle v2 from a Single Build

Perform the procedure below to create a Release Bundle v2 from a single, selected build.

  1. In the Application module, select Artifactory > Builds.

  2. Click the name of the desired build, and then select Create Release Bundle from the actions menu.

    GA_create-rb.png

    Tip

    Alternatively, click the name of a specific Release Bundle version and then click Create Release Bundle.

  3. In the Release Bundle Details tab of the New Release Bundle window, do the following:

    1. Enter a name for the Release Bundle. (If a Release Bundle was previously created from the selected build, its name will appear.)

    2. Enter the version number of the Release Bundle.

      Note

      Naming restrictions:

      • The name is limited to 32 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.

    3. [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).

  4. Click Next.

  5. 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.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.

    GA_new-release-bundle_content-tab.png

    Note

    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 buildInfo.env.RBV2_MANIFEST.Create Release Bundle v2 Version

  6. (optional) Select the Include Build Dependencies checkbox to have the Release Bundle include the dependencies associated with the build.

    Important

    Dependencies must be located in local or Federated repositories to be included in the Release Bundle. Dependencies located in remote repositories are not supported.

  7. Click Create. The Release Bundle appears on the kanban board and as an event in the Release Bundle version timeline.