Use this source type to create a Release Bundle v2 version from one or more packages. The Release Bundle can contain packages of multiple types, such as Docker, Maven, PyPI, and so on.
Security: Requires Read permissions to source artifact repository 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 packages.json
Consumes: application/json
Sample Request:
{ "release_bundle_name": "rbv_2", "release_bundle_version": "1", "skip_docker_manifest_resolution": false, "sources": { "source_type": "packages", "packages": [ { "package_name" : "commons", "package_version" : "1.0.0", "package_type" : "maven", "repository_key" : "commons-dev-maven-local" } ] }, }
The request includes the following information:
Property | Type | Description |
---|---|---|
| string | Release Bundle name. |
| string | Release Bundle version. |
| boolean | Determines whether to skip the resolution of the Docker manifest, which adds the image layers to the Release Bundle. The default value is |
| string | Should be set to |
| string | Describes the packages to include in the Release Bundle, as described below. |
| string | The package name. |
| string | The package version. |
| string | The package type (Docker, Maven, etc.). |
| string | The repository key where the package is located. |
Sample Response: See here for an example.