Note that you can mix Groovy DSL build scripts with Kotlin DSL ones, i.e. a Kotlin DSL build script can apply a Groovy DSL one and each project in a multi-project build can use either one.

     */
    GradleExecuter withEnvironmentVars(Map<String, ?> environment);

    @Deprecated
    GradleExecuter usingSettingsFile(File settingsFile);

    GradleExecuter usingInitScript(File initScript);

    /**
     * Uses the given project directory
     */
    GradleExecuter usingProjectDirectory(File projectDir);

    /**
     * Uses the given build script
     */
    @Deprecated

    protected
    abstract val processOperations: ProcessOperations

    /**
     * Configures the classpath of the init script.
     */
    @Suppress("unused")
    open fun initscript(block: ScriptHandlerScope.() -> Unit): Unit =
        internalError()

    /**
     * Logger for init scripts. You can use this in your init script to write log messages.
     */
    @Suppress("unused")

`-D`, `--system-prop`::
Sets a <<build_environment.adoc#sec:gradle_system_properties,system property>> of the JVM, for example `-Dmyprop=myvalue`.

`-I`, `--init-script`::
Specifies an <<init_scripts.adoc#init_scripts,initialization script>>.

`-P`, `--project-prop`::
Sets a <<project_properties.adoc#sec:project_properties,project property>> of the root project, for example `-Pmyprop=myvalue`.

`-Dorg.gradle.jvmargs`::

    }

    @Test
    fun `script handler belongs to the current script`() {

        val init = withFile(
            "some.init.gradle.kts",
            """
            println("init: ${'$'}{initscript.sourceFile}")
            """
        )

        val settings = withSettings(
            """
            println("settings: ${'$'}{buildscript.sourceFile}")
            """
        )

     */
    protected TestFile settingsScript(@GroovyBuildScriptLanguage String script) {
        settingsFile.text = script
        settingsFile
    }

    protected TestFile initScript(@GroovyBuildScriptLanguage String script) {
        initScriptFile.text = script
        initScriptFile
    }


    protected TestFile getSettingsFile() {
        testDirectory.file(settingsFileName)

                    <ul id="other-developing-topics">
                        <li><a href="../userguide/working_with_files.html">Working with Files</a></li>
                        <li><a href="../userguide/init_scripts.html">Initialization Scripts</a></li>
                        <li><a href="../userguide/dataflow_actions.html">Dataflow Actions</a></li>
                        <li><a href="../userguide/test_kit.html">Testing with TestKit</a></li>

"""
    }

    def "reasonable error message for dependencies of init scripts which are missing from verification file"() {
        file("init.gradle") << """
            initscript {
                repositories {
                    maven { url "${mavenHttpRepo.uri}" }
                }
                dependencies {
                    classpath 'org:foo:1.0'
                }

include::sample[dir="snippets/buildCache/developer-ci-setup/groovy",files="settings.gradle[tags=developer-ci-setup]"]
====

It is also possible to configure the build cache from an <<init_scripts.adoc#sec:using_an_init_script,init script>>, which can be used from the command line, added to your Gradle User Home or be a part of your custom Gradle distribution.

.Init script to configure the build cache
====

This may cause these directories to no longer be searched or backed up by some tools. To disable it, use the following code in an <<init_scripts#sec:using_an_init_script,init script>> in the Gradle User Home:

====
[.multi-language-sample]
=====
.init.gradle.kts
[source,kotlin]
----
beforeSettings {
    caches {