• Type: Bug
• Resolution: Unresolved
• Priority: Minor
• Component/s: pipeline-stage-view-plugin
• Labels:

  None

[JENKINS-44193] wfapi/describe execNode empty - I need to query which node a stage runs on via rest call.

James Sandlin created issue - 2017-05-10 18:21

James Sandlin made changes - 2017-05-10 18:23

Summary

Original: wfapi/describe execNode empty

New: wfapi/describe execNode empty - I need to query which node a stage runs on via rest call.

James Sandlin made changes - 2017-05-10 18:25

Description

Original: We use pipeline on a scale of 64+ nodes. We utilize the wfapi/describe endpoint extensively to track and report stage execution to a custom server. When a stage fails or takes too long, I am required to go from our reporting server over to Jenkins then goto the logs of the run then search for a known substring of our server naming standard so I can figure out where I need to ssh / debug issues or what grafana page I need to view to analyze resource utilization.   Please add the value of execNode in the wfapi/describe OR another endpoint. I understand some stages run on master & the default value can remain empty.

New: We use pipeline on a scale of 64+ nodes. We utilize the wfapi/describe endpoint extensively to track and report stage execution to a custom server. When a stage fails or takes too long, I am required to go from our reporting server over to Jenkins then goto the logs of the run then search for a known substring of our server naming standard so I can figure out where I need to ssh / debug issues or what grafana page I need to view to analyze resource utilization.   Please add the value of execNode in the wfapi/describe OR another endpoint. I understand some stages run on master & the default value can remain empty.   I find JENKINS-35634 appears to ask the same, but it is closed as a dup of JENKINS-26138, which seems unrelated.

James Sandlin made changes - 2017-05-10 18:30

Description

Original: We use pipeline on a scale of 64+ nodes. We utilize the wfapi/describe endpoint extensively to track and report stage execution to a custom server. When a stage fails or takes too long, I am required to go from our reporting server over to Jenkins then goto the logs of the run then search for a known substring of our server naming standard so I can figure out where I need to ssh / debug issues or what grafana page I need to view to analyze resource utilization.   Please add the value of execNode in the wfapi/describe OR another endpoint. I understand some stages run on master & the default value can remain empty.   I find JENKINS-35634 appears to ask the same, but it is closed as a dup of JENKINS-26138, which seems unrelated.

New: We use pipeline on a scale of 64+ nodes. We utilize the wfapi/describe endpoint extensively to track and report stage execution to a custom server. When a stage fails or takes too long, I am required to go from our reporting server over to Jenkins then goto the logs of the run then search for a known substring of our server naming standard so I can figure out where I need to ssh / debug issues or what grafana page I need to view to analyze resource utilization.   Please add the value of execNode in the wfapi/describe OR another endpoint. I understand some stages run on master & the default value can remain empty.   I find -JENKINS-35634- appears to ask the same, but it is closed as a dup of JENKINS-26138, which seems unrelated.     ex: {code:java} { "_links": { "self": { "href":"/job/job_name/44/execution/node/16/wfapi/describe"} } ,"id":"16","name":"Setup for build","execNode":"","status":"SUCCESS","startTimeMillis":1494429943607,"durationMillis":320,"pauseDurationMillis":0}] }{code}

Jesse Glick made changes - 2017-05-30 21:58

Component/s		New: pipeline-stage-view-plugin [ 21139 ]
Component/s	Original: workflow-api-plugin [ 21711 ]