How to override caching in Gradle

Published by Tomas Zezula on

Gradle is smart enough to skip running tasks if there haven’t been any changes compared to the previous build. This post shows how to override the default optimisation to ensure the given task is executed every single time.

Let’s create a sample project:

mkdir hello-gradle && cd $_ && gradle init --type java-library

Build it:

gradle build
...
:test
:check
:build
BUILD SUCCESSFUL

Now let’s pick the test task and run just that one with a debug option on:

gradle test -d
...
0:46:52.653 [INFO] [org.gradle.api.internal.tasks.execution.SkipUpToDateTaskExecuter] Skipping task ':test' as it is up-to-date (took 0.073 secs).
10:46:52.654 [DEBUG] [org.gradle.api.internal.tasks.execution.ExecuteAtMostOnceTaskExecuter] Finished executing task ':test'
10:46:52.654 [LIFECYCLE] [class org.gradle.TaskExecutionLogger] :test UP-TO-DATE

The task was skipped as expected. Removing the build destroys the cache and makes the tests re-run:

gradle clean test -d
...
10:50:01.966 [INFO] [org.gradle.api.internal.tasks.execution.SkipUpToDateTaskExecuter] Executing task ':test'

The project cleanup however can be avoided by applying the rerun-tasks flag:

gradle test --rerun-tasks

The tests will run again, but without the need to clean the build first.

Categories: Build AutomationTips & Tricks

Tomas Zezula

Hello! I'm a technology enthusiast with a knack for solving problems and a passion for making complex concepts accessible. My journey spans across software development, project management, and technical writing. I specialise in transforming rough sketches of ideas to fully launched products, all the while breaking down complex processes into understandable language. I believe a well-designed software development process is key to driving business growth. My focus as a leader and technical writer aims to bridge the tech-business divide, ensuring that intricate concepts are available and understandable to all. As a consultant, I'm eager to bring my versatile skills and extensive experience to help businesses navigate their software integration needs. Whether you're seeking bespoke software solutions, well-coordinated product launches, or easily digestible tech content, I'm here to make it happen. Ready to turn your vision into reality? Let's connect and explore the possibilities together.

Related Posts

Failed Gradle build
Kotlin

Gradle Multi-Module Builds: Setting Up Shared Dependencies

When you are managing a multi-module Gradle project, more often than not you'd want to share certain dependencies across different modules. This is particularly true for test dependencies. You can achieve this by defining common dependencies in the root build file and applying them to all subprojects. However, a problem often encountered is the dreaded Unresolved reference: testImplementation error. This blog post suggests a simple trick that resolves the issue. Give it a go and happy testing ever after!

Kotlin

Keep Data Safe in Multi-Tenant Systems: A Case for Supabase and Row Level Security

When managing multi-tenant systems, one common anxiety is that a coding error can unintentionally expose user data. Incorrectly routing a user's data to the wrong tenant, or even distributing it to another user within the same tenant, is a very real fear. Additional precautions are necessary to safeguard against human errors. Supabase is an open-source platform that offers a viable alternative to Firebase. Similar to Firebase, it provides a frictionless user authentication process. Due to its integration with Postgres, it supports sophisticated access controls at a row level, aptly referred to as Row-Level Security (RLS). In this article, we'll explore a concrete example of leveraging this feature and provide step-by-step implementation guidelines.

Featured image
Stripe

Stripe Payment Links and Custom Parameters

As of now, Stripe's Payment Links don't offer the flexibility of adding custom fields beyond those available in the API. The fields that you can directly pass into the Payment Links endpoint are complementary identifiers like prefilled_email or client_reference_id. This post shows some of the workarounds you can use to enrich your payment links with additional custom parameters.