Slave conflict when using multiple Jenkins instances

XMLWordPrintable

    • Type: Bug
    • Resolution: Won't Fix
    • Priority: Minor
    • Component/s: jclouds-plugin
    • None

      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.

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

              Created:
              Updated:
              Resolved: