New: Task Inputs Visibility for Gradle Builds
Ever wonder why today’s build is 3x slower than yesterday’s, even though nothing seems different? We’ve just launched a solution.
The new Task Inputs tab in Bitrise Build Cache gives you complete visibility into your Gradle task execution. Now you can see exactly which tasks ran, why they didn’t come from cache, and what inputs changed between builds.
What’s New
When you open any Gradle invocation in Build Cache, you’ll find a new Task Inputs tab showing:
- Top slowest tasks with execution times and expandable details
- Complete input properties for each task - see compiler options, plugin configs, toolchain versions, and more
- Input and output file trees showing every file involved in task execution
- Cacheable status for each task so you know if optimization is even possible
- Filter and search to quickly find the tasks you care about
How It Helps
See details for a single invocation: View complete input properties and file trees for each task in the Task Inputs tab.
Compare invocations for maximum insight: The real power comes from the Compare page (accessible via the Compare button on any invocation detail page or from the invocations list), where you can compare task inputs between two builds side-by-side. This is the fastest way to:
- Debug slow builds by seeing exactly what changed at the task level
- Fix cache misses by identifying which specific input properties or files changed
- Spot configuration bugs that cause cache key invalidation
Optimize with data: Make informed decisions about build configuration by understanding the full picture of what impacts each task.
The Compare page also includes AI-generated summaries that automatically highlight key differences between invocations.
Try It Out
The Task Inputs tab is live now. Open any Gradle invocation in Build Cache and check it out - you’ll find it alongside your Critical path, Uploads & Downloads, and other tabs.
Let us know what you think and how it helps with your build optimization efforts.