Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-38099

Node reported as local if executor is busy

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Fix
    • Icon: Minor Minor
    • node-sharing-plugin
    • None

      I configured a new job and tried to restrict its execution to the label which is provided by Foreman only.
      If I have an busy executor (performs the built in that time) with the same label, I cat get such a hint from Jenkins:

      is serviced by 1 node and 1 cloud


      This isn't true because the label is serviced by the (Foreman) cloud only.

      When the running build ends, the message changes to

      is serviced by 1 cloud

      which is correct information.

      If it is possible to distinct between nodes connected directly and nodes provided on-fly by a cloud, this should be taken into consideration when the hint is constructed.

            pajasoft Pavel Janoušek
            pajasoft Pavel Janoušek
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: