Release Bundle v2 Creation Errors Collected by System

JFrog REST APIs

Content Type
REST API

When using the REST API for Release Bundle v2 version creation, set the optional query parameter to fail_safe=false to have Artifactory collect the following validation errors and return them as a group after the failed creation operation:

Error Code

Sample Errors

400

  • Source artifacts not found

  • Invalid source artifact (checksum mismatch; prohibited package types; multiple paths for same package type; multiple binaries on same path)

  • Attempt to create from repo that is not local or Federated

  • Attempt to use application version as Release Bundle source

403

  • No read permissions to Release Bundle, build, or artifact in repo-path

404

  • Repo-path not found

422

  • Unresolvable build artifact

Note

The errors listed in the table above are meant to be representative but are not an exhaustive list.

When fail_safe=true (default value), the creation operation will fail as soon as the first validation error is encountered.

Other types of errors, such as 403 errors due to permissions or an expired key and 409 errors due to attempts to create a version that already exists, are not supported by the fail_safe option.

Tip

By default, a maximum of 50 errors are returned. The limit is defined by the system property lifecycle.errors.group.limit