yep - the tool installation fails but doesn't report in the step log (you have to see full log). Annoying. I think correct way is to have the failure reported to the log for the step (will open an appropriate ticket) - have seen this myself but was waiting for it to appear int eh real world. Blue Ocean uses the pipeline api, so there isn't much it can do here (other than resort to showing full log).

vivek the bismuth stuff may help here, not sure.

Looking at classic stage view - it isn't much better. It doesn't show the specific error for the log for that step (which seems wrong). However, it does show it in a mouseover that you can sometimes see. Which is unreadably formatter, but implies the data is there somehow...

ON mouse over you see the missing tool error:

To confirm when you look at logs in classic you don't see it either:

vivek assigning you to take a look if there is something we can do. I think I will open a ticket against the tool step.

Actually no closing this - moving instead to a pipeline bug.

Thank you michaelneale (read sarcasm), you closed a real problem marking it as a duplicate of the similar but fundamentally different problem, that describes the issue in such a specific way, no one will ever fix it.

The real problem here is that the error that causes the step to fail is not captured in the logs for that step.  And if your trying to run anything more than a toy project its near impossible to find the error in the main log since it now lumps ALL output from every node together.  Think about when people are running 20 parallel steps.  How the hell do you find the output?

This new interface has the potential to be really powerful, but when a simple command fails, or is aborted by timeout / job cleanup / slave going off line you can't see why.  The step just goes red.  Basically ALL output within the { step... } logs needs to be included in the logs here.

Not fixed, not Minor, re-opening because its causing us and others alot of pain. Many people are talking about this sort of problem when you Google for a bit.

ottago so you are saying it isn't just about the "tool installation" step but potentially any step type (where the log goes missing) - in that case nes, that is too narrow and this isn't a dupe. This can't be solved by blue ocean or the stage view however, something deeper has to be looked at. Many steps in the year  since this was closed have been updated to report errors in the log, but if there are other ones, and possible examples, they would be good. 

I am not sure what you mean "many people are talking about this" - can you be more specifc? 

When this was opened it was purely about the tool installation (in the example given) - which was covered by that other ticket at the time. I am not sure the sarcasm helps if you are looking for a resolution 

ottago please open a ticket with reproduction instructions on the latest Jenkins LTS + plugin installs and we'd be happy to look into it. Typically if something has regressed, we don't reopen old tickets that might match the problem as the report could be bogus for a number of different reasons.