-
Bug
-
Resolution: Unresolved
-
Minor
-
None
Some Pipeline errors not showing up in Blue Ocean. In the screenshotted Pipeline, there was a system failure on the Jenkins side when trying to handle the scheduling of a node.:
Resuming build at Wed Oct 10 14:33:36 GMT 2018 after Jenkins restart Waiting to resume part of Core » jenkins » PR-3689 #1: ‘win2012-79a800’ is offline Waiting to resume part of Core » jenkins » PR-3689 #1: ‘win2012-79a800’ is offline Waiting to resume part of Core » jenkins » PR-3689 #1: ‘win2012-79a800’ is offline Waiting to resume part of Core » jenkins » PR-3689 #1: ‘win2012-79a800’ is offline Waiting to resume part of Core » jenkins » PR-3689 #1: ‘win2012-79a800’ is offline Waiting to resume part of Core » jenkins » PR-3689 #1: ‘win2012-79a800’ is offline Resuming build at Wed Oct 10 14:43:26 GMT 2018 after Jenkins restart Waiting to resume part of Core » jenkins » PR-3689 #1: ??? Waiting to resume part of Core » jenkins » PR-3689 #1: ‘win2012-79a800’ is offline Waiting to resume part of Core » jenkins » PR-3689 #1: ‘win2012-79a800’ is offline Waiting to resume part of Core » jenkins » PR-3689 #1: ‘win2012-79a800’ is offline Waiting to resume part of Core » jenkins » PR-3689 #1: ‘win2012-79a800’ is offline Waiting to resume part of Core » jenkins » PR-3689 #1: ‘win2012-79a800’ is offline Waiting to resume part of Core » jenkins » PR-3689 #1: ‘win2012-79a800’ is offline Waiting to resume part of Core » jenkins » PR-3689 #1: ‘win2012-79a800’ is offline Waiting to resume part of Core » jenkins » PR-3689 #1: ‘win2012-79a800’ is offline Waiting to resume part of Core » jenkins » PR-3689 #1: ‘win2012-79a800’ is offline Waiting to resume part of Core » jenkins » PR-3689 #1: ‘win2012-79a800’ is offline Waiting to resume part of Core » jenkins » PR-3689 #1: ‘win2012-79a800’ is offline Waiting to resume part of Core » jenkins » PR-3689 #1: There are no nodes with the label ‘win2012-79a800’ [Pipeline] End of Pipeline GitHub has been notified of this commit’s build result ERROR: Killed hudson.model.Queue$BuildableItem:ExecutorStepExecution.PlaceholderTask{runId=Core/jenkins/PR-3689#1,label=win2012-79a800,context=CpsStepContext[11:node]:Owner[Core/jenkins/PR-3689/1:Core/jenkins/PR-3689 #1],cookie=7a4c0793-cd41-4c06-9ac0-b4b1c712818b,auth=null}:4 after waiting for 300,000 ms because we assume unknown Node win2012-79a800 is never going to appear! Finished: FAILURE
Which unfortunately doesn't show up at all in Blue Ocean, unless you dig into the raw pipeline.log artifact.
