-
Bug
-
Resolution: Unresolved
-
Minor
-
None
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 appears to ask the same, but it is closed as a dup of JENKINS-26138, which seems unrelated.JENKINS-35634
ex:
{ "_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}] }
Hi,
I have the very same problem described in this issue, but there hasn't been any activity on this. Has anyone looked at this?
Thanks