LambCI – A continuous integration system built on AWS Lambda

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.

[ Parent | on HN ]

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.

https://github.com/klarna/eremetic

[ Parent | on HN ]

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?

[ Parent | on HN ]

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.

[ Parent | on HN ]

Re:LambCI – A continuous integration system built on AWS Lambda by dominotw on Sunday July 10, 2016 @02:45PM (#12066662)

but first build always take a hit making the build times unpredictable making build time regressions hard to track.

[ Parent | on HN ]