Create a Release Bundle (v2) from a Single Build

JFrog Artifactory Documentation

Products
JFrog Artifactory
Content Type
User Guide
ft:sourceType
Paligo

When you want to create a Release Bundle v2 from a single build, it is possible to do this directly from the Builds table instead of going to the Release Lifecycle dashboard.

To create a Release Bundle v2 from a single build:

  1. In the Application module, go to Artifactory > Builds.

  2. Click the name of the build to be used to create the Release Bundle.

  3. From the actions menu on the right, select Create Release Bundle.

    GA_create-rb.png

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

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

    3. Select a signing key.

  5. Click Next.

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

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

  8. Click Create.

Note

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