...
Setting Name | Description | Default Value | ||
|---|---|---|---|---|
Default Pipeline | Default pipeline will be automatically assigned to new Releases under this folder. The pipeline on the Release can still be changed for scenarios where you don’t want to use the default. | n/a | ||
Default Branch Name | The branch name default set on each Project and Package when creating a Snapshot. The branch can also be set on each item from the Definition tab, or on the Create Snapshot form. | n/a | ||
Snapshot Name | A custom script used to generate default Snapshot names. | CurrentDate | ||
Do not allow duplicate file(s) | New snapshot creation will fail if a file is present in more than one Package from the same Project in a Release. See Additional Notes for how this setting impacts different methods of creating a Snapshot. | false | ||
Do not allow approvals by code committers | Prevents FlexDeploy users from approving a gate if they had made commits to any of the source code deploying on that stage. This applies for both Approval and External Approval Gates. Checks for matching username or email in commit details. Administrators can still override.
| false | ||
Do not allow overriding external approvals | Prevents manually overriding an External Approval Gate within FlexDeploy. Note that if this setting is enabled and your CMS system is down, you will be unable to progress your Release. However, Administrators can still override. | false | ||
Complete Package after deployment to production | All Packages in a Snapshot will be marked as completed once the Snapshot has successfully completed the a production stage on the Pipeline. The completed packages will be skipped during future Snapshot creation and pipeline execution. Note that this will cause issues in the event that a production stage is not the last stage in the pipeline or there are multiple production stages. The packages will be completed once the first production stage is successful. Packages can be reactivated again.
| false | ||
End Release after successful production stage | Release will be marked as Completed once a Snapshot has completed the production stage of a pipeline. Note that the Release will end once the pipeline execution is successful and a production stage was present. All pending Snapshots and running pipeline executions will be aborted. Release can be reactivated again. | false | ||
Lock Comments | Prevents new comments after the Release has been completed. | false |
...