This message was deleted.
# configuration-caches
Slackbot
03/09/2023, 8:29 AMThis message was deleted.
m
melix
03/09/2023, 8:29 AMThey typically start Docker containers, and test assumptions verify the number of started containers, etc.
melix
03/09/2023, 8:30 AMThe easy path for me was to not enable parallel builds, but as soon as I have the configuration cache enabled, then hell freezes over, because everything gets executed in parallel.
melix
03/09/2023, 8:31 AMso tests start to fail because of the configuration cache being enabled
melix
03/09/2023, 8:32 AMis it expected that parallel execution is enabled despite
org.gradle.parallel--no-parallel🤔 1
c
CristianGM
03/09/2023, 9:02 AMUse a shared buildlservice to limit parallelism between them
m
melix
03/09/2023, 9:02 AMI know, but that is not the question 😉
melix
03/09/2023, 9:03 AM(and I'm implementing this right now, but this is not as trivial as it seems, since I need a way for each project to declare what kind of resources it uses)
a
Adam
03/09/2023, 9:39 AMm
melix
03/09/2023, 9:41 AMThanks @Adam, I think the docs could be clearer: in particular that it doesn't care about the
org.gradle.parallel--no-parallel--no-parallelmelix
03/09/2023, 9:43 AMTo be clear, I think it's arguable because once CC is enabled by default (if), then the behavior of builds would change.
melix
03/09/2023, 9:47 AMin case one is interested with the solution I have put in place: https://github.com/micronaut-projects/micronaut-test-resources/pull/182
😍 1
melix
03/09/2023, 10:03 AMand as a bonus: https://github.com/gradle/gradle/issues/24253