This message was deleted.

I guess you talk about the one in the gradle user home? Would be bad if it did by default as that would mean the test runs different depending on who runs it. The TestKit tests have separate gradle user home directories to be isolated and reproducible. If you want the ones from the executing user in there, it is probably easiest you copy them in.

isn’t this the point of init scripts though?

Yes, but not to tests of a project. Tests should be written in a way they work everwhere self-contained, and run the same everywhere. A test should not behave different just because someone else is executing it.

in my case I have a CI machine that uses init scripts to setup Gradle to use a Nexus proxy… buildsystem tests now cannot resolve dependencies because they don’t execute the init script and try to use repositories directly.

Maybe somehow extend the init script to manipulate test tasks to inject init scripts or something like that?

ended up with:

systemProperty("gradle-init-scripts",   gradle.startParameter.allInitScripts.join(File.pathSeparator))

and then:

private static GradleRunner gradleRunnerWithInitScripts(Path projectDir, String ... arguments) {
  return GradleRunner.create().withProjectDir(projectDir.toFile()).withPluginClasspath()
          .withArguments(concat(of(getProperty("gradle-init-scripts").split(File.pathSeparator))
                  .flatMap(initScript -> of("--init-script", initScript)), of(arguments)).collect(toList())
          );
}