Add ability to set default/global values for more than just the global execution timeout of a deployment step. Settings include:
Machine contact timeout
Fail overall Deployment Plan is not successful
Only run other Deployment Steps if successful
These are currently all found in the advanced filters section of a deployment step.
Why Is It Needed
Customers are setting Machine contact timeout on a per-step basis to control the overall time a deployment takes to complete. This is time consuming and repetitive.
Having this be set globally, at the deployment level, and overridden at the step level provides much greater flexibility and value.
Description
Add ability to set default/global values for more than just the global execution timeout of a deployment step. Settings include:
These are currently all found in the advanced filters section of a deployment step.
Why Is It Needed
Customers are setting Machine contact timeout on a per-step basis to control the overall time a deployment takes to complete. This is time consuming and repetitive.
Having this be set globally, at the deployment level, and overridden at the step level provides much greater flexibility and value.
Related Issues and Tickets
Acceptance Tests
N/A
Done Checklist
┆Issue is synchronized with this Gitlab issue by Unito