autonomousapps/dependency-analysis-gradle-plugin

Cache misses between CI and local

Open

#1,083 opened on Dec 22, 2023

View on GitHub
 (18 comments) (1 reaction) (0 assignees)Kotlin (154 forks)auto 404
enhancementhelp wantedperformancesponsorable

Repository metrics

Stars
 (2,172 stars)
PR merge metrics
 (PR metrics pending)

Description

Build scan link

Plugin version 1.28.0

Gradle version 8,5

JDK version 17

(Optional) Kotlin and Kotlin Gradle Plugin (KGP) version 1.9.21

(Optional) Android Gradle Plugin (AGP) version N/a

Describe the bug The buildHealth task and all its deps are not being cached properly and we get cache misses more often than ideal. The cause seems to be not using PathSenstivity.Relative in all cases. The reason we get cache misses is because the absolute paths of input dependencies of many of the tasks created by the plugin use absolute or none path sensitivity. See image for one such example

To Reproduce Steps to reproduce the behavior:

  1. ...

Expected behavior If the code hasn't change I expect cache hits for all the tasks that this plugin creates in CI.

Additional context

Contributor guide

Research direction
Review the Gradle task configuration for buildHealth and related tasks, focusing on input properties and their PathSensitivity. Identify where absolute paths are used and change to PathSensitivity.RELATIVE where appropriate. Check the plugin's source code for @InputFiles or @PathSensitive annotations.
Tech stack
kotlinjava
Domain
build system
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GradleKotlin
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70