Allow the usage of vNets from another resource group than the one used to deploy the agents into

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

ExportXMLWordPrintable

      A lot of people need to connect the VM agents to other Azure resources through an existing VNet. It would be very nice if the existing VNet can reside in a different resource group.
      There's already a PR for this: https://github.com/jenkinsci/azure-vm-agents-plugin/pull/11 It has to be cleaned up a bit

            Assignee:
            Dayang Shen
            Reporter:
            Claudiu Guiman
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: