Re:LambCI – A continuous integration system built on AWS Lambda
by somesaba on Wednesday July 06, 2016 @07:24PM
(#12046534)
Cool! I had an idea for something like this but instead of having each build be it's own lambda event, I wanted to make each individual test it's own lambda event. The goal is to have the build time for a complex project boil down to the time it takes to setup + run the longest test.
[ Parent
| on HN ]
Re:LambCI – A continuous integration system built on AWS Lambda
by adamb on Wednesday July 06, 2016 @10:11PM
(#12047112)
Have you written any code to that effect? I've been trying to think through how booting up dependencies might work (for things like integration tests).
I have aspirations for QA (https://github.com/ajbouh/qa) to learn this trick, but it needs some lambda-specific smarts before it gets there.
Re:LambCI – A continuous integration system built on AWS Lambda
by falsedan on Thursday July 07, 2016 @12:52AM
(#12047531)
We're doing something similar, but using mesos. We bundle tests up, so we don't have to eat the setup costs for every test, and try tracking test pollution by splitting bundles when they fail & running them separately, again.
Re:LambCI – A continuous integration system built on AWS Lambda
by not_yet_a_dalek on Thursday July 07, 2016 @03:13AM
(#12047926)
That is more or less the same reason I started the eremetic framework. We were tired of dealing with the trouble of using a lot of VMs as jenkins-slaves, and long test suite runtimes.
Re:LambCI – A continuous integration system built on AWS Lambda
by dominotw on Thursday July 07, 2016 @01:34AM
(#12047632)
where do you store build caches? npm/gems ect?
Re:LambCI – A continuous integration system built on AWS Lambda
by falsedan on Thursday July 07, 2016 @03:20PM
(#12051533)
Dependencies? On the host; they're ephemeral but they'll run multiple builds between coming into existence and disappearing.