ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #gradle
Stale task outputs with configuration cache active On Gradle 8.4 and later, enabling the configuration cache alongside the build cache appears to change which task input properties participate in the cache key. The documented behavior is that the configuration cache serializes the task graph once and reuses it, while the build cache keys task outputs on decl
Goal Decide whether the production pipeline should enable Gradle's configuration cache, which serializes the task graph at configuration time for faster builds. Constraints Local runs often use a warm Gradle daemon and a populated ~/.gradle directory, while CI agents start cold with a clean GRADLE_USER_HOME . Plugins may perform unsupported work at execution
Goal: Ensure build cache invalidates when files change outside declared inputs. In many projects, external tools or manual edits modify files that are normally outputs of a Gradle task. Since the build cache only hashes declared task inputs, these external changes are invisible to Gradle, leading to stale artifacts being reused. Constraints: Gradle’s current
Android Gradle Plugin Migration The Android Studio AGP Upgrade Assistant automates the migration of build scripts to newer plugin versions to ensure alignment with the IDE release. To optimize build performance, many projects enable the Gradle configuration cache, which persists the output of the configuration phase. When the Upgrade Assistant modifies the b
I just updated Android Studio and started a new project. But now the project grade file seems different. Here are the lines: plugins { id 'com.android.application' version '7.1.0' apply false id 'com.android.library' version '7.1.0' apply false } task clean(type: Delete) { delete rootProject.buildDir } Now, for example, I need to paste the Firebase lines in
Assuming Gradle 8.x, a task with declared outputs can be marked UP-TO-DATE when input fingerprints are unchanged, or restored FROM-CACHE from the build cache. Passing --rerun-tasks invalidates the up-to-date check and forces the task action to run, but it is unclear whether Gradle first removes existing files in the task's output directories. The precise goa
Goal Our team wants a repeatable development environment using Gradle dependency locking so resolved dependency versions stay consistent across local machines and CI. Gradle writes lockfiles recording resolved versions, repositories, and metadata. During a normal build, Gradle does not automatically regenerate these lockfiles; if resolution would change a re
When a Gradle build runs a database schema migration via the sql plugin or an integrated tool, a failed statement may leave the database in an inconsistent state if the transaction does not fully roll back. The sql plugin's transactional=true flag attempts to wrap each statement in a JDBC transaction, but its reliability depends on the driver's behavior and
Integration Boundary The Gradle Daemon lifecycle (governed by org.gradle.daemon.idletimeout ) and sporadic build invocation patterns form an integration boundary where static configuration meets variable workload demand. The daemon terminates after a fixed idle period—defaulting to three hours—regardless of when the next build might arrive. Goal and Constrai
androidstudio
android