Pipelines fail very silently if a step is waiting on a step that is undefined anywhere else.
so
`- label: "First Step"
...
label: "Second Step"
dependsOn: "some-non-existent-step"`
Will fail but it wont indicate why, it just will complete first step successfully and never start second step and fail.
In a complex pipeline this can be a hard one to pinpoint, a missing 'key' basically. An error annotation saying "key "some-key" not found" would be great
Pipelines fail very silently if a step is waiting on a step that is undefined anywhere else.
so `- label: "First Step" ...
Will fail but it wont indicate why, it just will complete first step successfully and never start second step and fail.
In a complex pipeline this can be a hard one to pinpoint, a missing 'key' basically. An error annotation saying "key "some-key" not found" would be great