Former Square in San Francisco. Former SoundCloud in Berlin. Now speeding up builds around the world at Gradle.
Improving Developer Experience with Gradle Build Scans
11:15 > 40 min
As a developer, you just want your builds to work but every now and then things go wrong and you need to investigate the build which sucks up a lot of your time not to mention context switching. In this talk we show you how build scans can help save a lot of time when you need to find build performance bottlenecks, investigate/troubleshoot CI failures, build/tool chain failures, visualize your dependencies, etc. to troubleshooting/investigating build issues and accelerate your builds/tests.
From this session you will learn…
- Can I make my build faster? Build performance profiling with a simple UI: what are all the performance bottlenecks in my build, how well is my build cache working, the impact of heap, garbage, dependency downloads on my build times.
- How well is my build parallelized? Can I get more parallelization to speed up my builds?
- What's happening in my build? View the build timeline view to see what tasks/goals are being executed in which order. You can use this to see how well parallelized is your build
- Git and CI integration for better workflow. Go from your CI job to your build scan and back. Go to the Git source repo, git commit id, show me all the builds on this git commit id
- Troubleshoot CI failures way faster with a build scan by viewing failed taks/goal in consol log. Build scans pull out all the details pertaining to your failure out of the consol log so you don’t have to parse through thousands of lines of logs
- Dependency Search: view, search through your projects dependencies and their versions in a few clicks
- Triage Test failures: The test dashboard sorts your projects test failures by failure count with a nice UI. With a few clicks you can see which test classes failed the most, sort by your longest tests, test methods with the most test failures, link to your test report
- Tool chain and build related failures: What’s breaking my build?
Common Cache issues in Android projects – 2023 Edition
14:55 > 40 min
In this talk, we will discuss some of the common Gradle build caching issues that Android developers face, and provide solutions to these problems.
We will begin by explaining what the Gradle build cache is and how it works. We will then outline the common issues that developers encounter when using Gradle build cache. These issues include incorrect build cache settings, conflicts with the build cache, and incorrect configurations.
Next, we will provide solutions to these issues. We will discuss how to configure the build cache settings correctly to ensure optimal performance. We will also explain how to resolve conflicts that arise when multiple developers work on the same project.
Furthermore, we will discuss how to optimize the Gradle build cache for large-scale Android projects. We will provide tips on how to manage the cache for multi-module projects and how to set up a distributed cache for teams working on a shared project.
In conclusion, this presentation provides a summary to common Gradle build cache issues in Android development. By understanding the issues and implementing the solutions presented in this talk, developers can optimize their build process and improve the overall efficiency of their development workflow.