-
Type:
Suggestion
-
Resolution: Unresolved
-
Component/s: Pipelines - Pipes
-
None
Hi team,
Currently - if you provide an incorrect pipe definition in your YAML configuration (for example: the pipe name is misspelled, or an incorrect version number is used), the following error is thrown in the UI:
No matching pipeline definition in the Pipelines configuration.
This error is confusing, and does not clarify what the actual issue is.
Can we please improve the error message so that it is clear that the pipe name was not found? For example:
The pipe "atlassian/dependency-scanner" was not found, please check the relevant documentation to ensure that the correct spelling and version number is configured in your YAML definition
Cheers!
- Ben (Bitbucket Cloud Support)