1. Use lambda function to trigger the jenkins jobs to make whole release pipeline.
2. Send the slack notification once the release with automated test is done.
1. Use lambda function to trigger the jenkins jobs to make whole release pipeline.
2. Send the slack notification once the release with automated test is done.
My automation test story is we moved from CircleCI to Jenkins, then to AWS. The benefit I can see is the maintenance and budget. Ops made this decision but it did not affect automation tests and the release pipeline too much, but I have seen the release pipeline has been developing much faster.
We use AWS Function and Jenkins API to trigger the Jenkins job from the AWS CodePipeline.
Since our automated deploy jobs are on AWS, and automated tests are on Jenkins.
Then we can create the release pipeline including AWS and Jenkins and put them together.
1. Cannot checkout code from GitHub but Jenkins can.
2. No shell script supported.
3. CodePipeline cannot send notification to Slack, but we can use Slack API and Lambda Function.
Pretty good.
For automation tests, it does not affect too much.
Our Ops are all AWS experts.
For automation developers, we do not care too much about which CI system we use. It does not affect us too much. Automation tests can be ran in most of mainstream CI systems.
AWS Lambda is a Code as a Service product. It is used for running code.
This product is easy to use.
The integration with other AWS products is straightforward. For our current usage, the integration that we have is sufficient. Everything is connected to CloudWatch and it's working.
I have been using AWS Lambda for one year.
AWS Lambda is a stable product.
This is a very scalable solution.
At this time, we don't anticipate increasing our usage.
The technical support is great.
The installation is straightforward and it only takes a few minutes to complete.
I deployed it myself.
This is a product that is pay-per-use, as opposed to a licensing fee. It could be cheaper.
There are no costs in addition to the standard pay-per-use fees.
I use other products that are in the AWS ecosystem, including AWS WAF.
In summary, this is a good product, it does what it is supposed to, and I recommend it.
I would rate this solution a ten out of ten.
