This message was deleted.
# community-supports
Slackbot
04/04/2023, 10:44 PMThis message was deleted.
e
Eric Haag
04/04/2023, 10:53 PM👋 Hey, @Shaun Reich! I hope I understand your question correctly.
The recommendation would be to not reuse project directories between tests.
In the documentation you linked, you can see that
@TempDir👆 1
c
Chris Lee
04/04/2023, 10:53 PMGive it a working directory that is transient so that nothing is cached. Or run with —no-build-cache
d
Dariusz Kuc
04/04/2023, 11:25 PM👋 personally I'd recommend to use composite builds instead of gradle runner -> it will be much faster
Dariusz Kuc
04/04/2023, 11:27 PM*well keep gradle runner it for failure scenarios and use composite build for happy path
s
Shaun Reich
04/04/2023, 11:30 PMoh yeah that's what I overlooked. looking at the sample code i have from gradle's site...i believe i stumbled on a docs bug (or perhaps used non-"current")...the code in the gradle samples i downloaded didn't use that feature. i'll try and track it down to file an issue for it - from
readme.mdShaun Reich
04/04/2023, 11:35 PM@Dariusz Kuc yeah, I'm inclined to agree..., from what little I know of the process, but the testing facilities at the plugin creation testing stage seem to lead me down this path and kts docs aren't always where I look. I have much to learn on Gradle still. Structuring build structures around can be challenging in little "gotcha" ways sometimes
6 Views