Tom

If you run self-hosted, expect this to look random across the fleet. Runners with a warm SDK directory sail through, and the moment one rebuilds its cache it joins the failures. Took me an hour to stop suspecting a specific machine.

The tell is that the failing step never reaches Gradle. If your build log dies before the first Gradle line, it is the SDK setup, not your project.