Gradle tasks order is not deterministic

[snicoll]

While working on code and build convention integration tests, I've noticed that the outcome of the test is not deterministic as the following two snippets are generated in reverse order depending of the bean processing order:

tasks.withType(KotlinCompile) {
	kotlinOptions {
		freeCompilerArgs = ['-Xjsr305=strict']
		jvmTarget = '1.8'
	}
}

and

test {
	useJUnitPlatform()
}

There's no obvious way to order those tasks but we could order the customizers that mutate the build.

[snicoll]

This seems to be limited to GradleBuid where we provide a name with a task (and several contributors can add attribue or customise it) but the writer has no way to order them. A naive approach could be that tasks are written according to their alphabetic order. Another would be that whoever calls the task first wins but I suspect neither are ideal.

[mhalbritter]

One idea would be to see if we can order the customizers (or their output) somehow so that more general configurations are on top of the more specific ones. In our example, the test configuration would always be below the tasks.withType(KotlinCompile) one, because it configures the test task, while the withType one configures all tasks with this type.