The Java development team at MS Open Tech has added a new contribution to the Hudson Continuous Integration plugin ecosystem with an update to our Hudson Azure Slave plugin. We’ve added the option to shut down (not delete) a Hudson slave after use, so it will be ready to spin up quickly the next time that you need it.
Here’s a screen shot of the new option in the Azure profile configuration:
Hudson Azure Profile Configuration
In September, the MS Open Tech Java Dev Team released the Hudson Azure Slave Plugin to enable developers and IT Pros to automatically provision and de-provision Azure virtual machines as Slaves to a Hudson Master. The plugin is open sourced on GitHub, and when used in conjunction with our Azure Storage Plugin for Hudson, enables management of Hudson and automatic deployment of artifacts to Azure very simple.
Getting Started with Hudson
For those of you who are new to Hudson, we recommend you review the GitHub documentation for setting up the Azure Slave Plugin and setting up the Azure Storage Plugin. For more information on how Hudson Masters and Slaves work, see this documentation on the Hudson site.
As always, we’re looking for ways to make it easier for developers to interact with all Azure services in any way we can, so if you have suggestion on what we can do to improve interoperability between Hudson and Azure, let us know!