This message was deleted.

We publish the distribution zip as a binary package to our internal nexus through conventional maven-publish (just configure the distribution zip as an artifact). We expose the checksum and nexus package url as part of the GitHub release description. Currently, setting up and updating the distribution (through the gradle wrapper task) is a manual configuration requirement for all of our engineering teams. We're investigating the introduction of a self-update mechanism in the distribution (some GitHub api calls to fetch available versions/releases and configuring and running the wrapper task through the distribution itself) in order to simplify that process.

Thanks! I've right now set it up using the "generic package" feature of Gitlab's package registry. I'm wondering if it would be possible to add support for using the checksum verification that Gradle does for the official wrapper. Or does gradle do this out of the box for custom distributions too?

When specifying a url for your custom distribution, if you provide a checksum the regular way, gradle will verify against it after downloading the wrapper binaries. There's no distinction between custom or official distributions.

Ah okay, so this is something that would be specified by the consuming gradle-wrapper.properties. Thanks!