We are happy to announce that the macOS tasks on Cirrus CI Cloud have switched to a new virtualization technology as well as overall architecture of the orchestration. …

Cirrus CI pioneered an idea of directly using compute services instead of requiring users to manage their own infrastructure, configuring servers for running CI jobs, performing upgrades, etc. Instead, Cirrus CI just uses APIs of cloud providers to create virtual machines or containers on demand. …

Cirrus CLI is a tool for running containerized tasks reproducibly in any environment. Most commonly, Cirrus tasks are used as part of continuous integration workflows but Cirrus tasks can also be used as part of the local development process as a hermetic replacement of helper scripts/Makefiles that don’t rely on…

Most Continuous Integration vendors try to lock you not only by providing some unique features that were attractive in the first place but also by making you write hundreds of lines of YAML configuration unique to this particular CI or by making you configure all your scripts in the UI…

Effective caching is by far the best option for speeding up your CI builds. You can optimize some computations and throw more CPUs on the problem but nothing is more efficient than just not doing the work at all by reusing cached results from some previous CI builds. All popular…

Google has a numerous Java libraries for almost all APIs on Google Cloud. Most of the libraries are using gRPC APIs which are very easy to integrate with Kotlin Coroutines since gRPC clients return ListenableFutures. Unfortunately, Google Storage doesn’t have a gRPC API and its Java library uses a blocking…

TLDR: Cirrus CI will start limiting how many CPUs user’s tasks are using simultaneously and not limiting how many tasks are actually running in parallel. Nothing will change if you are using the default 2CPUs/4G configuration for your tasks. But you can also get 2X parallelism if your tasks don’t…

Imagine you are loading some objects via an API. For example, you are loading values from a key-value storage. Most likely, your underlying implementation is using Dispatcher.IO or a custom dispatcher to execute the actual calls to the key-value store’s API. …

It’s always hard to hear that fellow DevTools startups have difficulties and had to close partially or fully. Last week GolangCI announced that they are going to shutdown their SaaS offering of GolangCI Lint (golangci.com). Congrats Denis Isaev and everyone involved on the run! 🙌 GolangCI.com is closing Dear customers of GolangCI.com,medium.com Cirrus CI already supported GitHub…