We have a large number of slaves configured to run on our multi-master jenkins installation.

We would like to to do the following:
1. We have setup a multi-master jekins installation using the jenkins gearman-plugin. We would like to share the slave configurations across multiple masters.
2. We run our slaves on the cloud and have created a separate application to automatically spin up slave machines and make them connect to the jenkins master. When new slaves are created/removed we would like to update the jenkins slave configurations.

Since the jenkins global config.xml contains configuration for master and slaves it makes the above use cases difficult. My suggestion is to de-couple the two configurations. Maybe put the slave config in another file.