Archive Releases

All completed and aborted releases are archived, which means that they are removed from the Digital.ai Release repository and stored in a different internal database, which is called the archive database. This improves performance and allows you to create custom hooks that export release information to external databases or reporting tools.

📄️ How Archiving Works

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

📄️ Create an Export Hook

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

📄️ Create a JDBC Export Hook

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.

📄️ Archive Database

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.

📄️ Clean up Stale Releases

See Configure Release and Trigger Settings.

📄️ Purging Archived Releases

Enable purging of archived executions