Inspiration
We have experienced many issues with the Cloudbees Jenkins Ecosystem and XLDeploy within FINRA in regard to performance, limiting the number builds and deployments can made within a day. Also, there are many overheads in maintaining and upgrading these softwares as well as infrastructure.
AWS Lambda Service just came out recently and appears to be a better solution to build a CD pipeline that scale automatically as it needs to, thus enable more builds and deployments to happens in parallel and at cheaper cost
What it does
Lambda CD Pipeline is a CD/CI pipeline that is highly scalable and configurable.
How I built it
The whole system is made up of a number of small Lambda functions and ECS tasks with only 1 specific responsibility (checkout, compile, test, deploy, etc...) that get triggered in a user-defined configuration (which specifies the sequencesv of the steps get executed in the pipeline).
Challenges I ran into
AWS Lambda run time environment is quite limited so we needed to make a good number tweaks to make one function works
Setting up AWS environment also took a large amount of time.
Accomplishments that I'm proud of
What I learned
How AWS Lambda works The limit when we use AWS service
What's next for Lambda CD Pipeline
We will keep implementing more Lambda function to make a complete CD pipeline
Log in or sign up for Devpost to join the conversation.