Issue

The JavaCompile tasks reference the stubs argument (through the check-framework-gradle-plugin) plugin which is defined as an absolute path to the checkerstubs folder.
When the project folder is different (CI vs local build for instance), this absolute path is different which changes the build cache key of the task and prevents from getting a build cache hit.

See related issue https://github.com/kelloggm/checkerframework-gradle-plugin/issues/252

Experimenting locally, the impact is 5mn28s of CPU time (starting with an empty cache):

Can only create thumbnails for attached images

Fix

The stubs argument can't be passed as a relative path because the JavaCompile task is leveraging the Worker API which changes the current working directory.
The fix is to use a CommandLineArgumentProvider which configures PathSensitivity not to be dependent on the path to the checkerstubs folder.