How fast are your Android CI builds? And why it matters.
Over time our Android CI builds gradually got slower and slower and before we knew it our CI build times were taking 47 minutes and frequently failing due to out of memory errors. The developers had complained quite a few times before but at the time we didn’t have any capacity to look into it. It was something that just snuck upon us and as we didn’t take any action I could see that the developers were just ignoring these build failures and working around it. Gradually it got worse and our build job history was just full of failed builds. We could no longer ignore these failures and decided to get help from our System/DevOps team and also decided to do some digging ourselves.
You can read more here.
Vice President of Strategic Accounts at Gradle, Inc
5 年Great post Mark Ng! Also check out the Gradle remote shared cache that can help bring those CI build times down by another 50% or so. Check out chapter five on this webinar. Dont forget to use the free build scan service for getting more insights to the performance of your build.? https://gradle.com/blog/improve-ci-performance-by-optimizing-maven-and-gradle-builds/