Use this source type to create a Release Bundle v2 version by collecting source artifacts from existing Release Bundle versions.
Note
If a single source Release Bundle is specified, this is the equivalent of a "clone" operation. If multiple source Release Bundles are specified, this is the equivalent of a "merge" operation.
Security: Requires Read permissions to source Release Bundle paths; 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 release-bundles.json
Consumes: application/json
Sample Request:
{ "release_bundle_name": "Tomcat-Bundle", "release_bundle_version": "1.0.0", "skip_docker_manifest_resolution": false, "source_type": "release_bundles", "source": { "release_bundles": [ { "project_key": "default", "repository_key": "release-bundles-v2", "release_bundle_name": "Commons-Bundle", "release_bundle_version": "1.0.0" }, { "project_key": "catalina", "repository_key": "catalina-release-bundles-v2", "release_bundle_name": "Catalina-Bundle", "release_bundle_version": "1.0.0" } ] } }
The request includes the following information:
Property | Description |
---|---|
| Should be set to |
| Determines whether to skip the resolution of the Docker manifest, which adds the image layers to the Release Bundle. The default value is |
Note
Each source Release Bundle in the request body may include a repository key, a project key, or both to specify the context from which it must be selected.
Sample Response: See here for an example.