Release properties

To specify metadata for a release or template, select Properties from the Show menu to go to the release properties page.

Release properties

To configure release properties:

  1. In the Release Name box, enter the name of the release. If the release is running, you can change its name.
  2. In Use risk profile, select a risk profile from the drop down list. If no risk profile is selected, the Default risk profile is used. For more information, see Configure profile risk settings.
  3. In the Description box, enter detailed information about the release. You can use Markdown language in this field.

    Under the description, you can see links to the template that the release is based on and, if applicable, the release that started it.

  4. Next to Flag status, you can select a yellow (attention needed) or red (release at risk) icon and enter a status message. Flagged releases are highlighted in overviews.
  5. In Start date and Due date, set the planned start and end dates of the release. Release uses these dates to show the release on the calendar. These are not the dates that the release actually started or ended.

    Note: You can set a release to start automatically at the specified start date by enabling the Start automatically on selected date checkbox. You can override this setting by manually starting the release. The default state of the Start automatically on selected date checkbox is disabled.

  6. Select the user responsible for the release from the Release Owner list. This user will receive additional notifications if tasks fail or are flagged.

    Release owners are automatically added to the Release Admin team when the release is created. This team has all permissions on the release.

  7. In Run automated tasks as user and Password, enter the user name and password of the Release user account that should be used to execute scripts in this release.
  8. If you want the release to be aborted when a task fails, select Abort on failure.
  9. Selecting the Allow passwords in all fields checkbox allows you to inject password values in non-password fields of custom script tasks. For example, for an Ansible plugin task, using a command line argument property, which is a string, you can pass a password variable like -Dusername=${ansibleUsername} -Dpassword=${ansiblePassword}, if the checkbox is enabled. Passwords values are masked in the UI and logging output but are decrypted before the task execution.
  10. Next to Tags, you can add tags to the release to make it easier to find in the release overview.
  11. Optionally add attachments by clicking Choose File next to Attachments. To delete an attachment, click the X next to it.
  12. To publish a link that you can add to a calendar application such as Microsoft Outlook or Apple iCal, select Publish link. If the release dates change, the event is automatically updated in your calendar.

    Important: Everyone who can reach the Deploy server can access this link, which may be a security concern.

  13. To download an ICS file that you can open with a calendar application, click Download calendar event.
  14. Under Release Variables click Variables Screen to enter values for the variables that have been defined in the release.
  15. Click Save to save your changes to the release properties. Changes are not saved automatically.

To discard your changes without saving, click Reset.