Tobias Henkel e207432a41 Move isChangeReadyToBeEnqueued after pipeline requirements ... When adding a change to a pipeline we have two filter steps before getting the change queue and doing further checks. The first one calls isChangeReadyToBeEnqueued which is used by the dependent pipeline manager to check if a change can merge. This causes potentially various api calls as this updates the change, analyzes status checks etc and thus is potentially expensive. The check for pipeline requirements is purely local and thus cheap. In many cases the pipeline requirements could filter out changes before the can merge check. Switching these two filters can save us some api calls and improve the performance of the scheduler run_handler loop. Change-Id: I3d3ea186e7852ae9c253d29f78dd5d7df81e71aa		2019-01-31 10:53:45 +01:00
..
__init__.py	Move isChangeReadyToBeEnqueued after pipeline requirements	2019-01-31 10:53:45 +01:00
dependent.py	Consider shared changes queues for relative_priority	2018-12-07 15:15:14 -08:00
independent.py	Consider shared changes queues for relative_priority	2018-12-07 15:15:14 -08:00
supercedent.py	Add supercedent pipeline manager	2018-06-14 16:32:03 -07:00