get_running_builds always returns empty list

Bug #1787430 reported by David Johannsson
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Python Jenkins
New
Undecided
Unassigned

Bug Description

python-jenkins 1.1.0
Jenkins 2.121.2

print server.get_running_builds()
[]

get_running_builds always returns an empty set

https://github.com/openstack/python-jenkins/blob/master/jenkins/__init__.py#L1437

INFO:root:{u'progress': 29, u'idle': False, u'likelyStuck': False, u'number': 0, u'currentExecutable': None}
INFO:root:{u'progress': 27, u'idle': False, u'likelyStuck': False, u'number': 1, u'currentExecutable': None}
INFO:root:{u'progress': 26, u'idle': False, u'likelyStuck': False, u'number': 3, u'currentExecutable': None}
INFO:root:{u'progress': 21, u'idle': False, u'likelyStuck': False, u'number': 2, u'currentExecutable': None}

This line always evaluates as false since currentExecutable is always None
if executable and 'PlaceholderTask' not in executable.get('_class', ''):

Revision history for this message
David Johannsson (davideaglephotos) wrote :

Seems like it is a jenkins bug https://issues.jenkins-ci.org/browse/JENKINS-49644 not returning currentExecutable

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.