Systems | Development | Analytics | API | Testing

When the engineering team first described what they wanted to build, I nodded along like I knew exactly what they meant. Gradle task inputs. Cache misses. Invocation diffs. Sure, totally. I wrote it all down and quietly Googled half of it afterward. That was my introduction to designing Gradle Task IO for Bitrise Build Cache, a feature built to help engineering teams understand why builds are slow and get more value from build caching.

For many teams, Bitrise Insights means build duration and failure rate. Those are good starting points to evaluate your CI performance, but they often fall short when it comes to understanding questions about speed and quality.

With Remote Build Execution (RBE) your Bazel build and test compilations run in parallel across many remote workers at once, instead of in series, one by one on a single machine.

Build tools have relied on it for years to avoid redoing work that hasn't changed. In React Native CI it's still a bit of a secret sauce: a fingerprint-based caching technique that can make your builds several times faster, yet one that surprisingly few teams have switched on. The premise is simple: most of the time you're only changing JavaScript, so most of the native modules are reusable.

In March 2024, Microsoft announced it would retire App Center in March 2025. For a lot of mobile teams, the first question was simple: what now? I was on the Release Management team at the time, and we thought CodePush was worth pursuing. We wrote up the case, got it onto the roadmap, and then waited. Nobody could say yet whether it would become a valuable product, and a team our size has to pick its bets carefully.

You’ve probably encountered the online conversations about GitHub’s AI scaling challenges. A lot of the chatter is about how forgiving (or not) users should be to GitHub in light of inexorable traffic increases but also GitHub’s own decision-making. There is certainly irony in the fact that it was a swashbuckling GitHub, against the objections of many open source developers, that pressed Copilot on the industry.

This year, AI agents have been writing more code than ever, and we've seen the slow part of shipping move from writing code to building and releasing it. You've probably felt it in your own team too. So this quarter we focused on making sure all that extra code doesn't turn into extra waiting for you. Here are the 20+ updates we shipped across Bitrise in Q3.

Most CI tooling makes you pick a side. Visual editing or code. Git as your source of truth or a decent place to edit. A config small enough for one file, or a modular structure your tooling flattens the moment you touch it. The Bitrise Workflow Editor does not ask you to choose. It meets your config where it lives. One file or forty, stored on Bitrise or in your repo. This post covers both, in that order.

That's Nathan Hillyer, Director of Engineering at ForeFlight, on what happened after his team started running their GitHub Actions workflows on Bitrise Build Hub. Until last month, trying that for yourself meant talking to sales first. That’s fine for a 300-person engineering org evaluating a CI overhaul, but it made no sense for the two-pizza team that just wants to know whether changing one line of YAML will meaningfully speed up their Xcode builds. That's fixed.

At Bitrise, we continually invest in security best practices to ensure that our customers' data stays safe and secure. As part of this ongoing effort, we are pleased to announce that we have successfully completed our 2026 SOC 2 Type II assessment, with no exceptions recorded in the final report. The report covers the period from July 1, 2025 to June 30, 2026 and is valid until June 30, 2027.