8 docs tagged with "archiving"

Release stores completed releases in a database that is separate from the repository: the archived database. Besides the completed releases, metadata for reporting is stored in this database.

See Configure Release and Trigger Settings.

This topic explains how to create a JDBC export hook in Release, allowing you to export data from the release system to a JDBC-compliant database. For more information, see Release export hooks.

You can use the export hook feature to configure Release to run a Jython script for every release that is about to be archived.

Archiving in Digital.ai Release is a two-stage process that manages completed and aborted releases:

Enable purging of archived executions

This article explains how to configure settings for releases, workflows, and triggers in Digital.ai Release. Settings are grouped by theme for easier navigation.

This topic explains how to start a new release from an archived release by using the original template and variable values