Description
Task name
ManualValidation
Describe your feature request here
In our CI pipeline, we use the Manual Validation task to make certain stages optional, such as the "Promote" stage responsible for publishing build artifacts, since not every build needs to be published.
However, with onTimeout: Reject, if the approval is not granted, the pipeline is marked as failed. While this mechanism does bypass the subsequent job or stage as intended, the resulting pipeline failure is unexpected and can be misleading.
This leads to two main headaches:
- Our pipeline dashboard fills up with "failed" runs that aren’t really failures, making it look like things are worse than they are.
- More importantly, it becomes difficult to distinguish between pipeline failures caused by real errors and those resulting from unapproved manual validations.
It would be beneficial if timeouts or even rejects in Manual Validation tasks could result in a neutral or skipped outcome, rather than marking the entire pipeline as failed. This change would make it easier to identify genuine pipeline failures and maintain a clearer overview of build health.
See also: How to fix "Ran for 14 days" build failure e-mails