Dry Run of Application Version

Creating an application version can be a heavy operation, especially when the version includes many dependencies or a large number of artifacts. If the version manifest contains errors, creation may fail.

Dry run mode lets you simulate the creation of an application version without actually persisting it. AppTrust performs all backend validations — verifying that sources (builds, for example) exist, artifacts are accessible, and the version name is valid — and returns a response with the results. No version is saved, no application version is actually created, and no audit or timeline events are generated.

This is particularly useful for validating CI/CD pipeline configurations before committing to a real version creation.

Key Capabilities

• Simulates version creation: Passes a dry_run=true parameter (API) or --dry-run=true flag (CLI) when creating an application version. AppTrust runs all validations identical to a real creation but does not save the version.
• Validation report: A successful dry run returns a report that includes the validation status, a summary of resolved artifacts, and confirmation that the manifest is valid.
• Error reporting: If the dry run fails, the response includes specific details about which artifact or validation failed, enabling faster debugging.

Dry Run vs. Standard Version Creation

You can perform a dry run of an application version using the:

• AppTrust API
• AppTrust CLI