Here's one to you devs. I just released my AWSEB Deployment Plugin, the newest version, and I've learnt a lot while improving it, specially when it comes to reusing other plugins (AWS SDK and AWS Credentials), but it left me wondering if it looks good or if there's any room for Improvement.
https://github.com/ingenieux/awseb-deployment-plugin/ It became a bit orthodox, as I wanted to allow Slaves finer control over credentials (thus allowing users to save credentials within a slave, or use IAM Instance Profiles - the recommended approach), but of course it requires running part of the code completely remote. Initially, I split the source due to Serializables and then wrapping into a Callable, but channel.call wouldn't log. Then, I tried to split into a CLICommand (meant to be called remotely), and I ran into a weird classloading issue where the CLICommand loaded, but classes from the same package didn't. Threw it away. Finally, I saw the remoting example and went into pipes. Had a couple of issues with blocking reads, and then decided to resort to getIn().available(), which seems to have done the trick. But I'm still curious and I'm sharing my experience in the hopes of someone being able to explain it to me. If any of you guys has some free time, I'd like to invite you to look at the source and bring me pull requests, or simply comments. Flames are welcome (sorta of) Thank you -- -- Aldrin Leal, <[email protected]> / http://about.me/aldrinleal -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CALpo8NsYTVZvCwhhone0dZ1ZwY777cx6GpbcAWfE6kiRexsH8w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
