My CI has a "release" job that is basically 1.

./gradlew testXYZ

2.

./gradlew assembleXYZ

Is there a better way to run those two commands so that I can make sure if

testXYZ

compiles my code, the

assembleXYZ

task can re-use that compilation? Or is that just by nature how gradle work and so no changes needed from my end?

you should get up-to-date on the tasks that testXYZ already ran. otherwise you'd want to compare build scans to see what inputs changed to cause them to re-run