-
Bug
-
Resolution: Fixed
-
Minor
-
-
2.321
Since JENKINS-65308 was implemented, we got several reports of provisioning issue.
In CloudBees, we've had for years an implementation of Cloud where {provision,canProvision} are implemented as remote calls. #canProvision should ideally return fast so we know it is not ideal, but this has gone really worse since JENKINS-65308 got implemented due to the increase of calls to Cloud#canProvision.
Something like JENKINS-57578 would likely clarify the situation, however in the current state, when calling trimLabels as part of a local operation (such as adding or removing a node), it would help if we only processed labels related to added or removed node(s).
- causes
-
JENKINS-68155 Jenkins.trimLabels(Node) does not properly update removed labels (regression in 2.321)
- Open
-
JENKINS-67635 Using "||" in pipeline targeting cloud labels cause multiple agents to be spun incessantly
- Closed
- is caused by
-
JENKINS-65308 Jenkins.trimLabels gets increasingly slower as number of nodes and labels increase
- Closed
- relates to
-
JENKINS-57578 Clarify & extend Cloud.canProvision(Label) API
- Open
- links to