Skip to main content
Version: Release 22.3

General Settings

This topic explains how to configure General settings in Release.

To configure Release, select Settings > General from the top menu. The General settings page is only available to users who have the Admin global permission.

Track changes in version control​

To enable the track changes feature:

  1. Go to Settings > General.
  2. In the Track changes in template version control section, select the Enable track changes checkbox.

Track changes

Release header color​

You can configure the color scheme of the Release header and menu bar items. For each type of your Release instance, you can define an associated color.

Select a color from the list and specify the name of you environment (for example: Production, Development). You can set a short description for the selected Release instance.

Header color

Reports​

Use the Reports section to configure thresholds used in the release value stream screen.

Reports Settings

Polling​

Use the Polling section to configure the polling interval to automatically refresh screens when task status changes (Status interval), or when tasks are added or deleted (List interval).

Polling Settings

In Release 8.6.0 and later, you can configure your company's logo.

Release has an option to upload your company's logo. Users with admin permission can upload a 26 x 26 pixel logo.

To enable the custom logo in XL-Release 8.6.0 and later:

  1. Go to Settings > General.
  2. Click the Choose file option under the Release header settings section.
  3. Choose your file and click the Save button.
  4. The logo is now displayed in the top header section.

These are the supported file formats:

  • gif
  • jpeg
  • png
  • svg+xml
  • tiff
  • x-icon (ico)

Custom Logo

Once configured, all notification emails from Release will display this logo in the footer.

note

It is not possible to replace the XebiaLabs Release logo through this setting.

Archiving​

Use the Archiving section to archive finished (that is, completed and aborted) releases. These releases are moved to a separate internal archive database so that the active repository can be kept relatively small.

Archived releases are available in reports and you can search for them from them Release Value Stream Mapping screen.

You can configure the time after which Release will archive a completed release. This is an amount of time since the release was completed or aborted.

You can also purge archived releases (from the archive database) that are being held after the expiration of the configured retention period. This allows for automatic cleanup of releases that are not required per your company's audit or governance policy.

The purge process is disabled by default and needs to be activated by the Administrator on the System settings -> General screen.

Before the releases are removed from the database, their content will automatically be exported to the file system location configured in the System settings. The exported releases will be organized in subdirectories by their end date so each zip will be in the purged/<year>/<month>/<day>/<release-id>.zip format.

Here's an example for the contents of a purged release zip file:

release.json
activity-log.json
attachments/<attachment-id>/<attachment-file-name>

Exempt Releases from Being Archived​

  • A new configuration option, Allow releases to skip archiving, has been added (System settings -> General) to exempt selected releases from being archived.

  • When this option is enabled, the Allow releases to skip archiving check box shows up on the template and release Properties sub-pages.

  • By marking a release to skip archive, the completed/aborted release is deleted instead of being moved to the archive database.

  • This is useful for transient releases, which has no business value and are to be excluded from reporting and statistics.

    Archiving Settings

For more information, see How archiving works.

note

Release reports related to finished releases only use data from the archive database. Therefore, if you configure a very long period before releases are archived, then your reports will not be up-to-date. Also, having a large number of releases that are not archived negatively affects performance. For more information about the configuration of the database, see Configure the archive database.

Trigger data purging​

This section is use to purge the Release Trigger execution data. These execution data will be removed from the database table.

To enable the trigger data purging:

  1. Go to Settings > General
  2. In the Trigger data purging section, select the Enable purging of trigger data checkbox.

You can configure the time after which Release will purge trigger data. This is an amount of time since the release was executed.

Trigger data purging

Release audit reports​

In Release, the generated release audit reports are stored as temporary files on a shared file system. These reports are available for a default period of 10 days after they are generated.

To configure the retention period for the generated reports in Release:

  1. Go to Settings > General.
  2. Under Release audit reports, in the Delete release audit report older than field, specify the maximum number of days the reports can be stored before automatically deleting them.