It's unclear to me how this is supposed to work for non-initial stages or parallel node acquisition.

jamesdumay we need to flesh this out a bit - as there are many cases where this "state" could happen, not just at the start. As Ryan said, it could be in mid pipeline and then need to obtain another node (eg in parallel) and get into this state. or some other infra could fail that would be relevant to show.

I think we need to reword this to be more general to get information as to what jenkins is doing into the flow nodes that blue ocean uses

michaelneale recampbell totally agree - there's a bunch of cases here but I don't know what they are. Seeking advice from the Pipeline experts

vivek when we do this I think we certainly want to represent it as a step or tie it to the nearest flownode that caused the message.

node ('something') {
stage('A') {
  node('first agent') {
  }
}

stage('B') {
  node('first agent') {
  }
}

stage('C') {
  node('first agent') {
  }
}
}

• waiting message for the "something" node should be for the whole pipeline (displayed as we do now with an empty state)
• A, B, C waiting messages should be tied to that stage, perhaps as a step so that we can show it inline with other steps.

We also need to explore other ways execution could be blocked. waiting on a node is one but are there more?

other ways execution could be blocked. waiting on a node is one but are there more?

Endless other ways.

also what the label expression/other deatils are

If there is anything missing, that would be a core bug, since that is where this CauseOfBlockage lives. The node step simply reports the message it is given.

Didn't mean to close this. Reopened.

vivek examples from today

pipeline {
  agent { label 'foo' } // While pipeline is blocked, solved by showing the message (no steps) that we have today
  stages {
    stage ('first') {
      agent { label 'bar'}
    }
    stage ('second') {
      parallel(
        "foo": {
          agent { label 'baz' }
        }
      )
    }
  }
}

// agent at pipeline level 

node ('foo') {
  stage(first) { ... }
  stage(second) { ... }
}

// how this translates from Script to Declarative

stage ('first') { // StartNode
  node ('bar') { // We know that this is executing? If so we want to display a synthetic step with CauseOfBlockage msg
    // Steps
  }
}

jglick I need to map a queued item corresponding to a node block to the FlowNode that is 'node' step. I need to do this so that I can show cause of failure to the stage whose execution is blocked.

Only way I think I can do is if I can get access to StepContext from PlaceholderTask object. Its private field. Can we expose it, something like StepContext PlaceholderTask.getContext()? This will let me do StepContext.get(flowNode) and associate it to the actual flow node so that I can associate it to right stage?

Here is the example declarative script. In this case we want to show stage 'first' as 'waiting for executor'.

pipeline {
  agent none
  stages {
    stage ('first') {
     agent { 
      label 'first' 
     }
     steps{
          sh 'echo "from first"'
      }
    }
  }
}

Include synthetic step in blocked stage node with name equal to reason for blockage.