We utilize multiple Octopus Deploy "instances" to logically separate our lines of business, but we currently utilize a single build server with appropriate permissions to keep the various lines of business users and jobs separate.

Our current CI solution allows us to define an Octopus Deploy instance and API key within the build steps, this allows a lot more flexibility than having a single global configuration, at the expense of a lot of repeated definitions. It would be great to have the best of both worlds with a multi-server global config that allows selecting the appropriate server per job configuration or Octopus Deploy step so we can deploy this via the Job DSL.