aws-lambda-jenkins-plugin
aws-lambda-jenkins-plugin copied to clipboard
XT-i
Jenkins plugin for AWS Lambda deployment
Seems like the plugin overrides to the default (No VPC, nor Subnets nor Security Group) when it updates code/config, so I have to manually config again these setting after each...
As per https://github.com/XT-i/aws-lambda-jenkins-plugin/issues/76 the current aws sdk version doesn't support eu-west-2. This version should provide the necessary support
Using 0.5.10 version of this plugin. When invoking publish new version and update alias procedure, I get the following error. java.lang.RuntimeException: java.io.IOException: Unable to serialize com.xti.jenkins.plugin.awslambda.publish.LambdaPublishServiceResponse@35fc939e at com.xti.jenkins.plugin.awslambda.publish.LambdaPublishBuildStep.perform(LambdaPublishBuildStep.java:66) at com.xti.jenkins.plugin.awslambda.publish.LambdaPublishBuildStep.perform(LambdaPublishBuildStep.java:46)...
Fix for https://github.com/XT-i/aws-lambda-jenkins-plugin/issues/75 The serialization error appears when the slave runs on external platform like ECS or other docker platform and the serialization fails.
When I zip a folder with zip function it adds all files that are in symlink folder. But when this module zips a folder it ignores simlinks.
We cannot select a value for the "Update Mode" as it has no options. This only happens in a specific Jenkins Job, not in every job. Please see attached image...
AWS CLI has ability to use file as payload: `aws lambda invoke --payload file://test_event.json` I tried to go the same way, but unsuccessful: ``` Payload: file://test_event.json ERROR: Build step failed...
In aws lambda deployment, able to fill aws access key id, aws secret key from credentials. See picture. Upgraded jenkins-ci version because of credentials plugin. zipped hpi file: [aws-lambda.hpi.zip](https://github.com/XT-i/aws-lambda-jenkins-plugin/files/2330312/aws-lambda.hpi.zip)
