From mobile apps to microservices, from small startups to big enterprises, Gradle helps teams build, automate and deliver better software, faster.

Gradle Community

distribution_path.rb

It's just the md5 of the distribution URL

```❯ ruby distribution_path.rb https\://services.gradle.org/distributions-snapshots/gradle-7.5-20220113070244+0000-bin.zip
/Users/dannyt/.gradle/wrapper/dists/gradle-7.5-20220113070244+0000-bin/bi5rojd82o5ohh86xxikkhdfe/gradle-7.5-20220113070244+0000-bin.zip%```

IIRC I couldn't pull this off in plain bash

bootstrap-gradle.sh

Here's roughly how I used it - this was so we could bootstrap Gradle and only download Gradle once. SDKMan, gng, etc might be a better choice now - this was many years ago

Or you simply run a short gradle build while building the docker image, letting the wrapper do its work. Then you also know it is properly done.

This was for a place where we didn't have the wrapper either, but yeah, using the wrapper jar to bootstrap from a generated properties file is probably the way to go

Fwiw, on CI I just use the `gradle:&lt;version&gt;` image from Docker hub, making sure that the version matches the one from the wrapper, and then use `gradle &lt;tasks&gt;` rather than `./gradlew &lt;tasks&gt;` ; i.e. the wrapper is actually only used on developers' machines.
This is because I don't need a specific JDK, Gradle distribution, or whatever, otherwise I'd probably build a Gradle image in a similar way, and use it the same, i.e. without the wrapper.

pretriggering the wrapper, thats so smart, thanks you all!

<@URQ797WRW> btw you mean to COPY the gradle-wrapper.jar into the image and running it?

but I need to copy the whole /gradle folder (gradle wrapper.jar, and gradle-wrapper.properties) + gradlew.sh?

Well, you could probably directly call the wrapper jar without the gradlew script, but it is probably easier to just copy it along