Closed bhebb closed 8 years ago
Facing the same issue. EnvInject password injection doesn't work with this. Most AWS plugins for Jenkins keep the creds in the admin area "Manage Jenkins".
There`s a version in the works with allows you to use the credentials plugin
-- Aldrin Leal, aldrin@leal.eng.br Master your EC2-fu! Get the latest ekaterminal public beta http://www.ingenieux.com.br/products/ekaterminal/
On Sun, Jan 25, 2015 at 2:59 AM, Myron Machado notifications@github.com wrote:
Facing the same issue. EnvInject password injection doesn't work with this. Most AWS plugins for Jenkins keep the creds in the admin area "Manage Jenkins".
— Reply to this email directly or view it on GitHub https://github.com/ingenieux/awseb-deployment-plugin/issues/15#issuecomment-71354635 .
Hi! I sent a pull request that should handle this issue, could you please take a look and merge it?
+1. I am also seeing this issue locally. It appears that this environment injection issue may not be applied to the AWS Access Key Id and AWS Secret Shared Key fields correctly. I get the following error:
Error Message: The request signature we calculated does not match the signature you provided. Check your key and signing method., S3 Extended Request ID:
Perhaps the signature is being calculated based on the field values BEFORE variable substitution?
Fixed. Now were relying on Credentials Plugin, so ensure your credentials are ported over.
Hi, How can I hide these informations : secret key ID and secret access with variables, properties file or using EnvInject Plugin?
Thanks
Stevens NELSON