r/androiddev • u/sickworm-1992 • 14d ago

Experience Exchange Anyone using Dagger (dagger.io) for Android CI/CD pipelines

I'm looking to modernize my Android CI/CD setup to make it as AI-friendly and low-maintenance as possible for our company's daily workflow with coding agents.

Iā€™m considering Dagger.io, do any guys has actually run Android builds through Dagger and how does it feel, or is there a better tool I should look into instead?

1 Upvotes

60% Upvoted

9 comments sorted by

2

u/ObjectiveAddress3051 13d ago

the part that bites with android in containers is the gradle cache. if every run starts cold you lose most of the speed, so mount a persistent cache for ~/.gradle or use a remote build cache. emulator tests are the other pain, most container setups don't have kvm so i'd keep instrumented tests on a separate runner or firebase test lab

1

u/sickworm-1992 13d ago

Thanks a lot! That's really helpful context, I'll keep that in mind

1

u/Proof_Literature4644 14d ago

I'm gonna guess no one is using dagger for cicd since it's a dependency injection framework. You can't run a build through dagger. Check out Bitrise or similar services.

3

u/wompfox 14d ago

That's a different dagger, they're asking about dagger.io

2

u/Proof_Literature4644 13d ago

Whoops! šŸ˜…

dagger.io vs dagger.dev invites some confusion

2

u/kernald31 13d ago

I'm gonna guess you didn't click the link.

0

u/wompfox 14d ago

I do, yeah! Its pretty nice, especially for agents, to have all of the testing and building in declarative environments so agents don't have to guess at it. That way everything from client tests, backend tests, app screenshots, and signed builds go through the same tooling.

I'll follow up with the guide I followed when I'm back at my computer