# Conservative defaults for this large multi-project build. CI or a developer with more headroom # can override these with -Dorg.gradle.workers.max=N / GRADLE_OPTS as needed. org.gradle.workers.max=4 org.gradle.jvmargs=-Xmx1g -XX:MaxMetaspaceSize=512m -Dfile.encoding=UTF-8 org.gradle.caching=true # Parallel project execution. It was tried before and reverted, because # `verifyCleanArchitectureDependencies` resolved every other project's `compileClasspath` from the # root and Gradle refused: a configuration belongs to its project, and reading it from elsewhere # asks for state held under another project's lock. The verification is now one task per module in # the project that owns the configurations, so the flag is a flag again rather than a defect. org.gradle.parallel=true # # Configuration cache is not enabled here, and the reason is narrower than it used to be. Measured, # not assumed: `ci`, `integrationCheck` and `releaseCheck` all store and reuse a configuration cache # entry with zero problems. The listener and `projectsEvaluated` callbacks that were named as the # blockers are not among them — the actual blockers were four tasks holding a `Configuration` in # their state, and those now hold a `Provider` instead. # # What is left is one task type: `ResolveConfigurationsTask` (`verifyDependencyLocks`, # `resolveAndLockAll`), which is `notCompatibleWithConfigurationCache`. Resolving every # configuration at execution time is not an implementation detail of that task, it is the task: # STRICT lock validation happens during resolution, so moving it behind a provider would move lock # verification into every build's configuration phase. Because the pull-request stage runs `:ci` and # `:verifyDependencyLocks` in one invocation, turning the flag on repository-wide would discard the # entry for that invocation anyway. Enabling it is therefore a change to how CI is split, not a # property — and scripts/ci/verify-configuration-cache.sh (main.yml) proves the storable half.