Jenkins allows some operations to be invoked through the CLI, including operations that are useful for configuring client controllers.
You can apply identical configurations to multiple client controllers by gathering all connected controllers from the command line and performing the operations on each one.
The list-masters CLI command on operations center provides information about all connected controllers in JSON format, allowing you to use that information to invoke commands on each client controller:
{ "version": "1", "data": { "masters": [ { "fullName": "my master", (1) "url": "http://localhost:9090/", (2) "status": "ONLINE" (3) } ] } }
| 1 | fullName - the name of the client controller, including folders. |
| 2 | url - URL for the client controller. |
| 3 | status - the connection status of the client controller. It can be 'ONLINE' or 'OFFLINE'. |
In August 2020, the Jenkins project voted to replace the term master with controller. We have taken a pragmatic approach to cleaning these up, ensuring the least amount of downstream impact as possible. CloudBees is committed to ensuring a culture and environment of inclusiveness and acceptance - this includes ensuring the changes are not just cosmetic ones, but pervasive. As this change happens, please note that the term master has been replaced through the latest versions of the CloudBees documentation with controller (as in managed controller, client controller, team controller) except when still used in the UI or in code.