This message was deleted.
# community-support
s
This message was deleted.
v
I guess we are taking about ephemeral build agents, and about downloading the distribution, not the wrapper, right?
How about using a docker image that has the wrapper(s) already present in the expected place, so that there is no need to download it from anywhere if a distribution is needed that is already present in the image?
āž• 2
t
^^ 100% that. then you just have to publish a new container for each gradle release you jump on
t
Thanks for your suggestions!
šŸ‘Œ 1
t
Fwiw, I use the
gradle
images, and do not use the wrapper on CI (i.e.
gradle
commands to use the Gradle version from the image, rather than
./gradlew
). You just have to make sure your
gradle/wrapper/gradle-wrapper.properties
and Docker image are using the same version.
In this case, the CI job is the "source of truth" for the Gradle version (the one of the Docker image), and the version in the gradle-wrapper.properties will be the one used by developers, so it'd better be the same to avoid unexpected behaviors. With the "embed the distribution in the Docker image" approach, the gradle-wrapper-.properties is the source of truth, and used by both developers and CI, and if there's a discrepancy with the Docker image you'll download the distribution on CI rather than use the one embedded in the image. It's a matter of trade-off.
t
Yep thanks a lot! i’m leaning towards having gradle-wrapper.properties to be the source of truth
šŸ‘Œ 1