From bafcda0040bf69e166fc80f165a94fff25cb6318 Mon Sep 17 00:00:00 2001 From: Jason Bedard Date: Thu, 25 Jun 2020 00:16:07 -0700 Subject: [PATCH] chore(docs): add testimonial from Allocadia --- README.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/README.md b/README.md index 5519cc19ab..96b0974b23 100644 --- a/README.md +++ b/README.md @@ -73,3 +73,12 @@ From [Lewis Hemens](https://github.com/lewish) at Dataform: > - A monorepo that scales: adding new libraries or packages to our repo became easy, which means we do it more and end up write more modular, shared, maintainable code > - Developing across machine types: our engineers have both Macbooks and Linux machines, bazel makes it easy to build code across both > - Developer setup time: New engineers can build all our code with just 3 dependencies - bazel, docker and the JVM. The last engineer to join our team managed to build all our code in < 30 minutes on a brand new, empty laptop + +From [Jason Bedard](https://github.com/jbedard) at [Allocadia](https://www.allocadia.com): + +> At Allocadia we use Bazel as the primary build system in a monorepo consisting of multiple applications, services and deployments across a range of technologies. Bazel has provided many benefits over previous build systems including: +> - reduced CI pipeline time from 60+ to 5-10 minutes +> - increased build and testing stability +> - improved developer ergonomics such as initial setup, faster more consistent local builds +> +> The use of rules_nodejs has provided these benefits across multiple Angular/TypeScript applications, Karma+Jasmine testing, Rollup, npm packaging, protobuf client/server communication, and a variety of Node.js based tooling. \ No newline at end of file