hfhbd
08/30/2026, 10:45 AMTanja Stojiljkovic
08/31/2026, 6:29 AMGradleTaskWarmUpService — it's part of the mechanism that populates the Gradle task list/run configuration dropdown, so I wouldn't recommend disabling it even if a way existed.
Better fix: instead of eagerly reading secrets in task configuration (System.getenv(...) / project.findProperty(...) directly), use the Provider API so it's evaluated lazily:
tasks.test {
environment("SECRET_KEY", providers.environmentVariable("SECRET_KEY").orElse(""))
}
This only gets evaluated at task execution time, not during sync/configuration, so the warm-up won't fail on missing secrets.
If you need a quick workaround in the meantime: IntelliJ sets the system property idea.sync.active=true during sync, so you can guard the eager code:
if (System.getProperty("idea.sync.active") != "true") {
// secret-dependent config
}hfhbd
08/31/2026, 6:32 AMtasks.test {
environment("SECRET_KEY", providers.environmentVariable("SECRET_KEY"))
}
I do want to not add a default value, because I need the value to be present when I run the task, but IntelliJ should not configure the task during sync.Tanja Stojiljkovic
08/31/2026, 6:42 AM