#DOCKER FOR MAC BETA CHANNEL MANUAL#
#DOCKER FOR MAC BETA CHANNEL ANDROID#
#DOCKER FOR MAC BETA CHANNEL CODE#
#DOCKER FOR MAC BETA CHANNEL WINDOWS#

The Google Cloud RBE was in alpha and had a waitlist when other out of the box solutions didn’t seem to exist. The big promise of reducing build times came when researching Google’s Goma and various remote execution backends for it. This required building and creating universal binaries, doubling the amount of macOS builds to be done. It might get fully built on top of Chromium at a future point in time.ĭecember 2020 brought another challenge which was about adding ARM64 builds for the new Apple M1 CPUs.

IOS followed suit with automation, being currently built as a framework that uses the core browser libraries.

#DOCKER FOR MAC BETA CHANNEL ANDROID#

Please note that Android was based on Chromium even before the desktop versions (but in a separate source control repository).

#DOCKER FOR MAC BETA CHANNEL CODE#

Our browser’s Android versions moved to use the same code as our desktop platforms in March 2020, thus targeting 8 different architectures (all built in parallel).

#DOCKER FOR MAC BETA CHANNEL WINDOWS#

Reproducible builds and cross-compiling were also of interest (for example building Windows binaries on Linux). For making builds cheaper we benchmarked various cloud instance types and tried builds in Docker. From various types of caching (Git, ccache, sccache, RAM disks) to running tests in parallel, reusing workspaces, reducing logging verbosity and more, we tried quite a few.

This put more focus on getting faster builds and many things were tried. No tests were initially being executed and the whole workflow took hours but once the foundation for automatic builds was laid, it was time to take care of continuous integration and allow developers to get early feedback across multiple platforms.Īround March 2019, we added a Nightly channel which would get built multiple times during the day but be pushed to our users 5-7 times a week. Meanwhile I came out with a proof of concept for a pull request builder that would produce and store desktop browser artifacts at every code change. 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.

#DOCKER FOR MAC BETA CHANNEL MANUAL#

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.

Docker for mac beta channel