compared with
Key
This line was removed.
This word was removed. This word was added.
This line was added.

Changes (4)

View Page History


|| Trigger || CI server || Jar version || AWS Lambda Aliases || lambduh properties ||
|1. Developer: push to Git \\ 2. mvn clean deploy |3. mvn lambduh:deploy-lambda |SNAPSHOT | DEV (reused), LATEST (reused) | withPublish=false |
|1. CI server: successful mvn release |2. mvn lambduh:deploy-lambda |<release ver> |TEST (reused), <release ver>* |withPublish=true |
|1. Manually in CI server |2. mvn lambduh:deploy-lambda |<release ver> | PROD (reused), <release ver>* | withPublish=true |
| | | | | |

* (version is same as version from jar file, but with "-" unstead of ".")

TODO: use complete lambduh:deploy-lambda command lines for each environment later. Easier to read.

|1. CI server: manually |Job: \\mvn lambduh:deploy-lambda -Dartifact=groupId:artifactId:version\[:packaging\]\[:classifier\] -Dalias=PROD -DremoteRepositories= |alias <version>* and withPublish=true is set automatically |If using the same AWS account for test and prod environment, this deployment can easily be done manually without a CI server job. |

* (version is same as version from jar file, but with "-" unstead of ".")


lambda-plugin will use http://maven.apache.org/plugins/maven-dependency-plugin/get-mojo.html under the hood to download artifacts