Status: Resolved (View Workflow)
- relates to
JENKINS-36547 Queue.Task.getFullDisplayName is a poor choice of key for LoadBalancer.CONSISTENT_HASH
I point out a possible regression in very unusual label setups in a recent PR comment. No opinion re LTS fitness.
Code changed in jenkins
User: Alexander Akbashev
JENKINS-48348 If task can be run only on master, use shortcut
Currently Jenkins to fire WorkflowJob re-calculates the ConstistentHash
for entire cluster even if there is no nodes were updated. If cluster is
big enough (>100 nodes), it becomes a problem, because MD5 is quite
expensive itself plus all this logic comes with high memory footprint.
Using the knowledge that WorkflowJob can be executed only on Jenkins master,
we can create a shortcut that does not do expensive calculation and just
returns Runnable or `null`.
(cherry picked from commit 00ccd23f6441a55bfd625660911d4bc79c7578ba)
It has been integrated towards 2.93