Description: Creates a new Release Bundle v2, uniquely identified by a combination of repository key, name, and version. For more information, see Understanding Release Bundles v2.
Since: 7.63.2
Usage: POST /lifecycle/api/v2/release_bundle
Usage restrictions
The {name} string is limited to 128 characters.
The {version} string is limited to 32 characters.
The {name} and {version} strings must begin with a letter, digit, or underscore.
The {name} and {version} strings must consist only of letters, digits, underscores, periods, and hyphens.
Query Parameters (optional):
Field | Type | Description |
|---|---|---|
| boolean | Determines whether the operation should be asynchronous (true) or synchronous (false). The default value is “true”. |
Note
See Common Optional Query Parameters for additional query parameters that are available for all Release Lifecycle Management APIs.
Request Header: X-JFrog-Signing-Key-Name (key-pair name to use for signature creation)
Note
See Create Key Pair for instructions about creating the key pair in Artifactory.
If the Release Bundle is intended for distribution using JFrog Distribution, you must propagate the key pair from Artifactory to the Distribution Edge nodes. For more information, see Propagate Public Signing Key.
You can create a Release Bundle version using any of the following source types:
Sample Response:
{
"repository_key": "release-bundles-v2",
"release_bundle_name": "Commons-Bundle",
"release_bundle_version": "1.0.0",
"created": "2023-05-18T07:41:47.023Z"
}Status Codes:
Code | Description |
|---|---|
200 | Submitted (async) |
201 | Created (sync) |
400 | Bad Request |
401 | Bad Credentials |
403 | Permission Denied |
404 | Not Found |
409 | Already Exists |