Hi all, In order to run the normal maven command line client, I need to pass various -D parameters to make SSL client certificates work, and this works fine.
Maven run via a Jenkins slave maven build however, no joy at all, all I get is a handshake error. As a result, maven is definitely not running with the correct -D parameters when spawned from a Jenkins slave. Is there a definitive process that allows you to pass -D parameters to maven? I have tried to add them to JDK options of the slave, but this makes no difference. I suspect that the JDK environment of the slave is not passed to maven when it is cranked up, but I cannot find anything to definitively prove this, or any documentation that explicitly describes Jenkins' behaviour. Regards, Graham -- -- You received this message because you are subscribed to the Google Groups "Jenkins Users" 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.
