We made changes to the Bitrise dependency cache offering. In short: having explicit and granular control on what to cache, sharing a cache across workflows, branches, and stacks, and automatically invalidating stale files in a cache.
If you’ve got an agile team interested in shipping fast without breaking things, this post is for you. In this piece, I’m going to explain how we at Rainforest QA approach automated testing in a continuous integration / continuous delivery (CI/CD) pipeline, with a focus on end-to-end (e2e) functional testing. The aim of our testing and other DevOps methodologies is to maintain a healthy balance between speed and product quality.
What is caching, and why should you care? In this article, we cover topics like what a cache is, how caching works, how it can speed up your build times, why you should cache your builds, and more.
Codemagic is now officially integrated with Runway, the DevOps platform for mobile. But wait, you might be wondering, isn’t Codemagic already that as a CI/CD for mobile? Aren’t the two services interchangeable? In fact, it’s quite the opposite — they’re powerfully complementary.
We have spoken in a previous blog post about documentation about how we believe that if you are building performance tests that support either Continuous Integration or Continuous Delivery then having to produce performance testing documentation before and after each test does not fit with this methodology.
In this article, we are going to learn how to create a custom Content Blocker for our WebView instances using the flutter_inappwebview plugin. Content Blockers are usually used for blocking ads, but you can also use them to block any other content. Blocking behaviors include hiding elements, blocking loads, and, on iOS and macOS, stripping cookies from WebView requests.
