Release Bundle v2 Auto-Creation

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

In addition to the methods you can use to create a Release Bundle v2, Artifactory can automatically create a Release Bundle v2 version, and attach related evidence, whenever you promote a build.Promote a Build

Release Bundles offer several advantages over build promotions. Release Bundles, even if they contain multiple package types, can be promoted with just a couple of clicks, eliminating the need for distinct promotions for each package technology. In addition, Release Bundles provide you with better visibility and control over your release candidate as it progresses through your SDLC. Release Bundles also feature an integrated method to capture evidence of the state of your release candidate and its readiness.

Auto-creation is not dependent on the method used for build promotion, whether you use your CI tool (for example, Bamboo or Jenkins) or the Artifactory REST API.Promote a Release Build when using the Bamboo Artifactory PluginJenkins Artifactory Plugin - Release ManagementBuild Promotion

Note

Release Bundle v2 auto-creation is controlled by an Artifactory setting for administrators. For more information, see Release Lifecycle Settings.

Note

Release Bundle auto-creation is currently supported for Cloud environments only. Support for Self-hosted environments will be added in a later release scheduled for the end of Q1 2025.

Auto-Creation Guidelines

The following guidelines apply to Release Bundle v2 versions created automatically during build promotion:

  • If the build promotion includes dependencies (dependencies=true), the Release Bundle promotion will include dependencies as well.

  • The type of build promotion determines the type of Release Bundle promotion:

    • If the build promotion is executed by moving the artifacts and dependencies (copy property set to false), the Release Bundle will be promoted to the target environment by moving its artifacts and dependencies.

    • If the build promotion is executed by copying the artifacts and dependencies (copy property set to true), the Release Bundle will be promoted to the target environment by copying its artifacts and dependencies.

    • If the build promotion involves a change of status without moving or copying the build's contents (artifacts and dependencies both set to false), no Release Bundle is created.

  • The Release Bundle name is identical to the build name, except that any special characters (aside from underscore, hyphen, and period) are converted to underscores (_).

  • The Release Bundle version is based on the build number.

  • If the length of the build name or build number exceeds the maximum valid values for a Release Bundle name (128 characters) or version (32 characters), build promotion continues but the Release Bundle is not created.

  • The value of the created_by property for the Release Bundle version is _system_.

  • If the status is defined for a build, the environment represented by that status is always given priority during promotion. For example, if an environment assigned to the targetRepo matches the status, the auto-created Release Bundle v2 is promoted to that environment. (That is, it is given priority over other environments that might also be assigned to the targetRepo.) If no environment exists for the status, a new environment is created for the promoted Release Bundle v2 with the name of the status, even when other environments are available.EnvironmentsPromote a Build

  • If the target repository (targetRepo) is part of a project, the environment for the auto-created Release Bundle version is project-specific as well.Projects

  • If the status is undefined, and the targetRepo has no environments assigned to it, auto-creation and promotion are not performed.