MN Summary: more information is needed than is exposed currently as steps in blue ocean (and possibly classic, but that isn't clear just yet) - more investigation needed. An unpleasant fallback is to resort to viewing full log, but that isn't obvious or nice.

It appears that the console output doesn't include the "node allocation" information which is useful when trying to debug systemic issues in Jenkins agents.

Take this Jenkinsfile which can execute on one of a number of agents. We had some issues where an agent was misbehaving, resulting in failures like:

WARNING: Failed to execute: select name,version,instanceid   from plugin where month >= 1466636926735         and name NOT LIKE 'privateplugin%'         and version NOT LIKE '%(private)'    order by name,version desc,instanceid because: [SQLITE_IOERR]  Some kind of disk I/O error occurred (disk I/O error)

LOLWUT aside, the beginning of the "classic" Console Output view includes:

Started by user rtyler
Replayed #8
Connecting to https://api.github.com using jenkinsadmin/****** (GitHub access token for jenkinsadmin)
[Pipeline] node
Running on kelp in /home/jenkins/agent-workspace/workspace/Infra/infra-statistics/master
[Pipeline] {
[Pipeline] checkout
Fetching changes from 2 remote Git repositories
Checking out Revision 4c2c3e9a24627421e7cd17d725a7a42bfe5a06e7 (master)
[Pipeline] tool
[Pipeline] tool
[Pipeline] stage (Sync raw data and census files)

A screenshot from the Blue Ocean detail page for this run is attached. Suffice it to say, there is no information in the detail page about what nodes this Pipeline run executed on