The Purge Settings define the configuration parameters to manage the archiving and purging of FlexDeploy execution data from the database repository, and purging of the artifacts stored in the artifacts repository.

...

Examples of configuring the purge

Scenario 1: Retain the last 3 successful builds in each environment/instance and keep the last 12 successful builds and last 2 failed builds overall. Artifacts will be purged from the file system after 15 days and execution data will be archived after 30 days. Data will remain in the archive for 365 days.

...

In this example, the only project versions that will be checked against the RETENTION_DAYS would be v9, v10, and v13. Those three version will only be purged/archived in they are older than the retention days parameters.

Defaults

The Defaults page provides a mechanism for configuring defaults for different objects using the Groovy scripting language. Select the Default Type to modify. Enter groovy script to define default values for variables described in the help text. Defining defaults helps in increasing productivity as these values are set as defaults when you create Endpoints, Projects, etc.

Each Default Type selection will list variables that can be set or used in a Groovy script. The script will be validated for syntax and variable usage on save. If an incorrect variable is used, the script will fail to save with an error message. You can setup a default value with just an assignment statement. For example, OsType="UNIX"; will return UNIX for the OsType variable. These variables are input to scripts, if they currently have a value for an object being modified/created. Defaults are mostly invoked when object is being created. Image Removed
The following sections describes the Default Types which are supported in FlexDeploy.