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

ability to restrict cloud slave usage

XMLWordPrintable

    • Icon: New Feature New Feature
    • Resolution: Unresolved
    • Icon: Minor Minor
    • openstack-cloud-plugin
    • None
    • Jenkins 1.651.3 on SuSe Linux

      I´ve configured and created a slave (docker-slave-xxxx) which is working pretty well.

      But I couldn´t find an option to restrict this slave to jobs that are labeled to this slave - so currently any job may be executed on this slave which is not desirable.

      For "normal slaves" there´s an option to choose between:

      • Only build jobs with label restrictions matching this node
      • Utilize this node as much as possible

      Currently I´m running into issues when one of my cloud-slaves is online, because some jobs require svn or other dependencies only available on master (or other, special slaves).
      The workaround is to restrict all jobs to be executed on master (or special slave) only...

          [JENKINS-42052] ability to restrict cloud slave usage

          Oliver Gondža added a comment -

          Right, this is now hardcoded to "NORMAL" mode (Utilize this node as much as possible).

          Implementation note: this needs to be reflected both on slave configuration side (so it will (not) pick the builds accordingly) as well as provisioning side (so it will not provision the machine just to find it will reject the task afterwards).

          Oliver Gondža added a comment - Right, this is now hardcoded to "NORMAL" mode (Utilize this node as much as possible). Implementation note: this needs to be reflected both on slave configuration side (so it will (not) pick the builds accordingly) as well as provisioning side (so it will not provision the machine just to find it will reject the task afterwards).

          Torsten Reinhard added a comment -

          Not sure if I understand it right: will there be any side-effect if this option would be available?

          With the current hardcoded "NORMAL" mode any job may potentially be executed on that (cloud) slave (if not explicitely tied to 'master') - and fail due to missing settings, tools or whatever (available on master or other slaves).

          Torsten Reinhard added a comment - Not sure if I understand it right: will there be any side-effect if this option would be available? With the current hardcoded "NORMAL" mode any job may potentially be executed on that (cloud) slave (if not explicitely tied to 'master') - and fail due to missing settings, tools or whatever (available on master or other slaves).

          Oliver Gondža added a comment - - edited

          Not sure if I understand it right: will there be any side-effect if this option would be available?

          No if we implement this carefully.

          With the current hardcoded "NORMAL" mode any job may potentially be executed on that (cloud) slave (if not explicitely tied to 'master') - and fail due to missing settings, tools or whatever (available on master or other slaves).

          Well, if it requires master you should tie it to master (not restrict everything else).

          Oliver Gondža added a comment - - edited Not sure if I understand it right: will there be any side-effect if this option would be available? No if we implement this carefully. With the current hardcoded "NORMAL" mode any job may potentially be executed on that (cloud) slave (if not explicitely tied to 'master') - and fail due to missing settings, tools or whatever (available on master or other slaves). Well, if it requires master you should tie it to master (not restrict everything else).

            olivergondza Oliver Gondža
            torstenreinhard Torsten Reinhard
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: