Source Type - Builds

Use this source type to create a Release Bundle v2 version by collecting source artifacts from one or multiple builds (also known as build-info).

By default, only build artifacts are included without dependencies. Dependencies located in local or Federated repositories can be included by adding the relevant property in the request body.

If the list of builds contains aggregated builds (containing one or more nested builds), these builds are resolved and included recursively.

A build may optionally contain a Release Bundle manifest, which defines which build contents are included in the Release Bundle. A manifest may be linked to a build during its creation using the property buildInfo.env.RBV2_MANIFEST. The manifest may be stored in any local or Federated repository and may be given an arbitrary file name. For more information, see Release Bundle Manifest for Builds.

Security: Requires Read permissions to build-info path, source artifact repository paths, and (optionally) the build manifest repository path; requires Read and Create permissions to the Release Bundles.

Usage restrictions: See here for details.

Sample Usage: POST /lifecycle/api/v2/release_bundle?project=default&async=false --header 'X-JFrog-Signing-Key-Name: my-signing-key' -H 'Content-Type: application/json' --upload-file builds.json

Consumes: application/json

Sample Request:

{
    "release_bundle_name": "Commons-Bundle",
    "release_bundle_version": "2.0.0",
    "skip_docker_manifest_resolution": false,
    "source_type": "builds",
    "source": {
        "builds": [
            {
                "build_repository": "artifactory-build-info",
                "build_name": "Commons-Build",
                "build_number": "1.0.1",
                "build_started": "2023-04-05T07:00:00.000+0200",
                "include_dependencies": false
            }
        ]
    }
}

The request includes the following information:

Sample Response: See here for an example.