Understanding Release Bundles v2

JFrog Artifactory Documentation

ft:sourceType
Paligo

Release Bundles group together the contents that comprise the bill of materials for your software releases. Each Release Bundle specifies the files and packages that comprise a release, along with their metadata. 

Release Bundles exist as a series of one or more versions, each of which must contain at least one artifact. Release Bundles may include source artifacts from local and Federated repositories only. A new Release Bundle can be created in several ways, including from builds, individual artifacts, AQL queries, or existing Release Bundles.

Note

Release Bundles cannot contain source artifacts that contain the same path and name from different repositories (known as a path collision).

Since all the artifacts specified in a Release Bundle are required to keep the release coherent, a Release Bundle version is immutable. Effectively, this means that once a Release Bundle version has been created, files cannot be added, modified, or deleted. In addition, any subsequent changes to the properties of the source artifacts are not reflected in the Release Bundle. To change a Release Bundle, a new version must be created.

Each Release Bundle is stored in a Release Bundle repository with a unique name and version per project.

Artifactory tracks all actions related to the Release Bundle version, including its creation, each time it is promoted to a new environment, and when it is distributed. This transparency increases customer confidence in the process that resulted in the software release.