Since I have a production system that relies heavily on the EC2 plugin, I'm considering a massive cleanup/reorganization of it, to take advantage of new things that Jenkins offers now (SSH Credentials plugin and other stuff). Along the way, I plan to introduce, where needed, some locking to protect the shared data structures that are being manipulated by multiple threads in Jenkins.
One thought occurred to me: since one of the primary uses of this plugin is to launch on-demand slaves that are connected via SSH, would it be possible to leverage what already exists in the SSH Slaves plugin, rather than duplicating all that stuff as is done now in the EC2 plugin? I've looked through the SSH Slaves plugin code and it doesn't appear like any provisions were already made for this, so I'm wondering what would need to be done for another plugin to be able to instantiate an SSH Slave itself and have the existing plugin code handle making sure Java is there and compatible, launching slave.jar, etc. Stephen/KK: Any thoughts on this approach? -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
