I want to continue the discussion on this feature request. I find that proposed enhancement quite appealing. We are currently reworking our Jenkins setup and will create custom AMIs for Windows that have all necessary tools installed (Java, Git, Maven, ...). It's trivial to also add an autostart script that starts a slave that connects to the master via JNLP. In fact I have that already working. The script takes the required connection information (master URL, slave name, and secret) from the instance's user data. Therefore the only piece that is missing is support for JNLP slaves in the EC2 plugin and the ability to start the instance with the correct user data. There are two major advantages over the current approach:
- It's much faster since WinRM isn't involved.
- It doesn't require SMB (especially not the almost dead SMB1 version)
I am willing to work on a pull request for this feature if there are good chances that it will be integrated into the official release. Any opinions on that? |