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

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

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Component/s: _unsorted
    • Labels:
      None
    • Similar Issues:

      Description

      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

        Attachments

          Activity

          Hide
          dayshen Dayang Shen added a comment -
          Show
          dayshen Dayang Shen added a comment - This is implemented in  https://github.com/jenkinsci/azure-vm-agents-plugin/pull/42

            People

            Assignee:
            dayshen Dayang Shen
            Reporter:
            clguiman Claudiu Guiman
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: