[JIRA] (JENKINS-49644) API does not return all running builds
Title: Message Title Mike Yang commented on JENKINS-49644 Re: API does not return all running builds This seems to be working again in `2.222.1`. And I think it was still broken as of `2.204`. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.188570.1519124859000.9781.1586797800223%40Atlassian.JIRA.
[JIRA] (JENKINS-49644) API does not return all running builds
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-49644 API does not return all running builds Change By: Andrew Bayer Component/s: workflow-durable-task-step-plugin Component/s: core Component/s: pipeline Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49644) API does not return all running builds
Title: Message Title
Graham Lyons created an issue
Jenkins / JENKINS-49644
API does not return all running builds
Issue Type:
Bug
Assignee:
Unassigned
Components:
core, pipeline
Created:
2018-02-20 11:07
Environment:
Jenkins 2.89.3, Pipeline 2.5
Priority:
Major
Reporter:
Graham Lyons
Fetching node information from a node running a pipeline build returns very little information about the executor. Hitting this URL - https://JENKINS_URL/computer//api/json?depth=2 - returns this about the executors:
...
"executors": [{
"currentExecutable": null,
"idle": false,
"likelyStuck": false,
"number": 0,
"progress": 5
}, {
"currentExecutable": {
"_class": "hudson.model.FreeStyleBuild",
"actions": [{
"_class": "hudson.model.CauseAction",
"causes": [{
"_class": "hudson.triggers.TimerTrigger$TimerTriggerCause",
"shortDescription": "Started by timer"
}]
}, {
"_class": "jenkins.metrics.impl.TimeInQueueAction"
},
...
The problem with this comes when we use the Python SDK because that uses the currentExecutable key to gather information about running builds: https://github.com/openstack/python-jenkins/blob/16007e01858cc5d36afdc31d22b5644f91a1f935/jenkins/__init__.py#L1149 We discovered this because the automation we use to scale our build cluster up and down doesn't see any jobs running on nodes which are running pipeline builds and so they get terminated mid-build. This did work with prev
