2 ms·
Very nice! This looks very close to the ideal CI infrastructure. I'm used to waiting on queues and long VM or container boots and configuration on other servic
by nzoschke 10y ago
Very nice!
This looks very close to the ideal CI infrastructure. I'm used to waiting on queues and long VM or container boots and configuration on other services.
We can almost certainly count on Lambda getting longer execution times and higher memory limits. We can also count on containerization solving the root problem.
We should also be building software with the goal of tests that run within reasonable limits like this.
`time make test` takes 39 seconds on my businesses Go projects. I'd consider a 5m test suite serious tech debt. The time that developers wait for feedback on tests and deployment is becoming a business bottleneck in the continuous delivery age.
- rgbrgb 10y agoWow, what's your secret to such fast builds? We're at ~35 minutes to build and test our rails monolith on Wercker. I'm guessing you're not hitting a db too much or loading phantomjs for end-to-end tests of a web ui?
- Intermernet 10y agoAt a guess, it's because they're using Go. The build and test processes are refreshingly (ludicrously) fast in that language. Note that doesn't mean you should switch to Go, as the ridiculously fast compile times could be outweighed by other factors (retraining, lack of specific features, etc.) I would however investigate it as an option as it seems to have found a place in the hearts of many former rails shops!