Pipeline with one failed and one running build should be marked failed
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Description
A common CI setup at our company is to have a first stage with two jobs, one for static analysis, and one for building/compiling. Static analysis takes 10-20 seconds, while compiling can take up to 30 minutes.
The problem is, if static analysis fails, the developer often doesn't know until the compile step completes. This is because there's no notification, and the pipeline is shown as running until all jobs in the stage complete.
It can be immensely annoying to wait thirty minutes for the build to complete only to find out that you have a spacing issue somewhere and will have to wait another 30 minutes.
Proposal
I think it would be reasonable to set the pipeline state as failed the moment any job fails.