How fast are your Android CI builds? And why it matters.

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.


Rooz Mohazzabi

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/

回复

要查看或添加评论,请登录

Mark Ng的更多文章

  • Auspost delivers on Jetpack Compose

    Auspost delivers on Jetpack Compose

    With Jetpack Compose’s first birthday just passing, many Android developer are probably thinking not if but when and…

    1 条评论
  • Kotlin Serialization — on the backend

    Kotlin Serialization — on the backend

    Continuing on our journey from the article “The first steps on your Kotlin Multiplatform journey — changing your…

  • Avoid CI/CD Lock-in — Make Your Builds More Portable

    Avoid CI/CD Lock-in — Make Your Builds More Portable

    We recently migrated our Android CI/CD pipelines from Bitbucket/Bamboo to Gitlabs. If you follow my blog, this is…

    1 条评论
  • Our Engineering Roadmap

    Our Engineering Roadmap

    We just completed our engineering road map for our Android apps at Australia Post. Each year we get together and try to…

  • Kotlin - The next enterprise language

    Kotlin - The next enterprise language

    The enterprise is dominated by 2 key programming languages Java and #C with many companies either choosing 1 or the…

  • Scaling an app for unexpected peaks

    Scaling an app for unexpected peaks

    It’s been an extraordinarily difficult time for many people and companies as we live through the Covid19 pandemic…

  • The first step on your Kotlin Multiplatform journey — changing your microservices.

    The first step on your Kotlin Multiplatform journey — changing your microservices.

    The mobile apps that we use today wouldn’t be very useful without APIs and the same can be said about APIs — without…

  • A Dependency Injection Showdown

    A Dependency Injection Showdown

    Choosing a dependency framework for your Android app is a big decision, it’s not something that you can easily replace…

  • How fit is your Android team in 2020?

    How fit is your Android team in 2020?

    A happy lunar year or happy new year if you follow the Gregorian calendar. It's a new year and that usually means new…

  • Kotlin Coroutines — Are we there yet?

    Kotlin Coroutines — Are we there yet?

    I got my first glimpse of coroutines at Chris Bane’s talk “Android Suspenders” at the 2018 GDG Melbourne Devfest. I…

社区洞察

其他会员也浏览了