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

Slave conflict when using multiple Jenkins instances

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      When using the same Google Compute Engine project (don't know if this happens with other providers, but I assume it does) to host slaves from multiple Jenkins instances, template/cloud quotas don't work as expected: slaves from both Jenkins instances are used when checking quotas instead of taking into account only slaves from that specific Jenkins instance.

        Attachments

          Activity

          Hide
          felfert Fritz Elfert added a comment -

          For that to work, jenkins would need to support clustering.
          Jenkins does not support clustering. So this actually works as designed.

          Show
          felfert Fritz Elfert added a comment - For that to work, jenkins would need to support clustering. Jenkins does not support clustering. So this actually works as designed.
          Hide
          felfert Fritz Elfert added a comment -

          Since version 2.10 of the plugin, there is a group-prefix per cloud (default: empty) which can be used to distinguish jenkins master instances.
          When accessing the same cloud profile from multiple jenkins masters, simply specify a unique string on each master.

          Show
          felfert Fritz Elfert added a comment - Since version 2.10 of the plugin, there is a group-prefix per cloud (default: empty) which can be used to distinguish jenkins master instances. When accessing the same cloud profile from multiple jenkins masters, simply specify a unique string on each master.

            People

            Assignee:
            pedro_ribeiro Pedro Ribeiro
            Reporter:
            pedro_ribeiro Pedro Ribeiro
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: