Building Code at Scale

QA
Зал №1

Тезисы

Applications are growing more complex. The back end may be microservices written in Java, Kotlin, and Go, while the front end may be JS. All these pieces are connected using gRPC. To make matters worse, the more people you add to a team, the slower everything gets. What if that wasn’t the way it had to be?

In this talk, we’ll follow a hypothetical team migrating to using Bazel for their builds, first locally, and then using distributed caching and distributed builds.

You’ll walk away with an understanding of how Bazel works, how it copes with a polyglot project, and how it can help speed up delivery. Of course, nothing is entirely perfect. You will also learn some of the pitfalls of using Bazel, and how you might be able to address them.

Аудитория и уровень

Anyone interested in how a build works. Enthusiasm is more important than expertise!


Selenium

Simon Stewart

Simon Stewart is the project lead for the Selenium project, and a coeditor of the W3C WebDriver specification. At Facebook he led the build tool team, was the tech lead for the Buck build tool project, and designed and helped develop the first iteration of Facebook’s mobile end to testing frameworks. At Google, Simon worked on Selenium and led the browser automation team as it scaled to running millions of tests per day. Simon lives in London with his family and dog.

Simon Stewart is the project lead for the Selenium project, and a coeditor of the W3C WebDriver specification. At Facebook he led the build tool team, was the tech lead for the Buck build tool project, and designed and helped develop the first iteration of Facebook’s mobile end to testing frameworks. At Google, Simon worked on Selenium and led the browser automation team as it scaled to running millions of tests per day. Simon lives in London with his family and dog.

Другие спикеры секции QA: