Skip to content

Gradle 9.7.0 and more configuration cache compatibility - #250

Open
labkey-susanh wants to merge 23 commits into
developfrom
fb_configCacheClasses
Open

Gradle 9.7.0 and more configuration cache compatibility#250
labkey-susanh wants to merge 23 commits into
developfrom
fb_configCacheClasses

Conversation

@labkey-susanh

@labkey-susanh labkey-susanh commented Aug 12, 2026

Copy link
Copy Markdown
Contributor

Rationale

Gradle 9.7.0 is the latest

Several tasks used for building and deploying needed own classes or property adjustments to become compatible with the configuration cache. Use of the configuration cache will be the default with Gradle 10, which is supposedly to be released sometime this year.

There are still some adjustments needed to adhoc tasks related to running tests before we can fully run on TeamCity with the configuration cache enabled. I'll leave this for a later PR.

Related Pull Requests

Changes

  • Update to Gradle 9.7.0
  • Convert verifyLicensePatch, patchApiModule, deployModule, undeployModule, symlinkNode, undeployModules to configuration-cache compatible tasks
  • Update ModuleFinder to not use deprecated hasProperty check that looks in parent project
  • Update ModuleDistribution and RunUiTest to be compatible with the configuration cache
  • Updates to MultiGit to mark as not configuration-cache compatible
  • Convert tasks that write out startup properties in TeamCity plugin to be compatible with the configuration cache
  • Update TestRunner's compileUITestJava task to be config-cache compatible and move the declaration of the aspectj configuration to that plugin

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant