![]() ![]() ![]() We also moved away from Azure to Amazon Web Services for Windows builds and from MacStadium to our own Apple machines for macOS builds. One of the big challenges was getting code signing right, and renewing certificates while keeping them safe. This allowed us to automate most of the manual steps and increase the predictability of outcomes. In a span of a few months we managed to code platform-specific pipelines in our continuous integration system and move away from the ad-hoc freestyle execution. This also proved to be a bottleneck, especially when trying to deliver on-demand updates on 3 channels: Release, Beta and Development (we had no Nightly channel at the time). ![]() The first aim was to stop doing manual and fragile builds (done on developer’s machines). When I first joined Brave in 2018, our browser was still based on Muon (our Electron fork) but switched to Chromium shortly after. Let’s get deeper into some challenges encountered when scaling the delivery of our browser – the principal vessel carrying features to our users.Īs a hands-on DevOps manager at Brave, I lead a global team of highly motivated engineers who not only keep things running smoothly and build new infrastructure, but also take pride in automation of build and release processes. These include browser and extension updates, lists for ad block and verified creators, background and Sponsored Images, ad catalogs, rewards transactions, private CDNs and proxies, infrastructure for Brave News, Brave Search, and many more. One might think that here at Brave we only deal with a few desktop and mobile applications but there’s an ever increasing number of backend services supporting our browser, private ads, and creator rewards ecosystem. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |