https://gradle.com/ logo
Join Slack
Powered by
This message was deleted.
# kotlin-dsl
s
This message was deleted.
c
I don't need them to be relocatable, I can use the same exact path in the "same" machine
p
They are already in the build cache
c
but not in the remote
could I enable the remote buildCache somehow? (using init script or any hacky way is fine)
I'm enabling CC in TeamCity builds for the most common tasks, but when we have a task that is not from CC we get things like:`Script compilation 1m 43.803s`
c
do you think that is your build scripts being compiled, or the Gradle distribution doing the first-time generation of API accessors etc? 1m43s is a fair chunk of time…
c
I've seen worst in this project..up to 3m I don't really know
c
ok. possible to run with --debug to get further deets?
c
I was trying to reproduce locally, but I didn't drop the right folder I guess
c
removing ~/.gradle/wrapper/dists will force a re-download and rebuilding of a few generated JARs. You’ll see log messages indicating this. If this is the case for your CI env that can be cached.
c
and BTW I think is just script compilation because I already ran in the same job 
./gradlew :help --configure-on-demand --dry-run
just to compile the included builds
c
ah ok. yes, run with --debug. Try clearing all of the project 
.gradle
folder.
c
:help task
Test task running after :help
c
wowsers. yes, bad compilation times. everything appears slow, though there are quite a large number of tasks.
c
it's a quite big project (backend, web, mobile apps, ... ALL in kotlin)
c
yea. while your stuff is on TeamCity, it may be worth looking at the GitHub gradle-build-action, to see what it caches. (not suggesting using it, just informational exploration)
c
yes, yes, I should take a look again
but.. does it cache the compiled scripts too??
c
Yes
p
Kotlin scripts should be put in the remote cache and be relocatable
The github action stores the local build cache because storing kotlin scripts would be redundant
If it doesn't work for you, debug log will confirm
c
Just to clarify be sure, I meant buildscripts, not kotlin-dsl plugins
p
Yep, same
c
How could something that is compiled before remote buildcache is configured, be stored in it?
p
Init scripts and settings script aren't in the remote cache, but project scripts are
c
oki, but then I think it's not working...maybe because we use a includeBuild plugin to set the remote cache?
p
Looks like it doesn't indeed
Debug logging should say something about compiled scripts caching
Open in Slack
PreviousNext
Powered by