Have the CI server provide the password as a Java property. That will be accessible to the build script.
Sooner or later, the CI server is going to have to have a secret that it exposes to the build script in order to decrypt the password. From a security standpoint, that secret is equivalent to the password. So why not just have it expose the password itself directly to the build script, and not muck around with encrypting/decrypting anything? Either that, or you'll need some kind of smarter authentication (a la SSH). ~~ Robert. On Fri, Mar 25, 2011 at 10:48 AM, Benjamin Muschko <[email protected]> wrote: > Thanks for pointing me to your plugin. I'll def. have a look. Unfortunately, > it's not for artifact uploading. I guess what I actually want is obfuscation > which is easy enough to implement with a key stored somewhere else. > > -- > View this message in context: > http://gradle.1045684.n5.nabble.com/Password-encryption-tp4264140p4264248.html > Sent from the gradle-user mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
