📄️ How Archiving Works
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.
📄️ 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
Release export hooks are a powerful mechanism you can use to define Jython scripts that export information about completed and aborted releases before they are archived.
📄️ 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
You can automate the cleanup of old releases by setting up a template with a cleanup script that will be periodically triggered by criteria that you provide. You can use this procedure in cases where many releases are in a failed state that are older than a specified period of time.
📄️ Purging Archived Releases
You can clean up the archived releases in the archive database by purging the archived releases.
📄️ Set up PostgreSQL Streaming Replication
A production setup in Release consists of an external clustered database to store operational and archived data from Release.