trimLabels calling Cloud#canProvision too often

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

    • 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).

            Assignee:
            Vincent Latombe
            Reporter:
            Vincent Latombe
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: