Catch all pipeline creation errors
Problem to solve
#35083 (closed) allows us to catch and report on errors for which the pipeline was not created due to insufficient permissions by the trigger author. However, there are additional errors that can prevent a pipeline from being created or continued. For example, failures because of CI/CD limits hit.
Intended users
Further details
Proposal
- If the pipeline fails to be created there currently is no mechanism to catch those errors.
- Set failure reason into the error state
Permissions and Security
Documentation
Testing
What does success look like, and how can we measure that?
What is the type of buyer?
Links / references
Edited by Fabio Pitino