Expand that row to see where the build applied this script.

image::performance/script-b-application.png[title="Showing the application of script-b.gradle to the build"]

You can see that subproject `:app1` applied the script once, from inside of that subproject's `build.gradle` file.

== Profile report

If you prefer not to use build scans, you can generate an HTML report in the

)
class JavaDependencyReportPerformanceTest extends AbstractCrossVersionPerformanceTest {

    def "generate dependency report"() {
        given:
        def subProject = (runner.testProject == LARGE_JAVA_MULTI_PROJECT.projectName) ? 'project363:' : ''
        runner.tasksToRun = ["${subProject}dependencyReport"]

        when:
        def result = runner.run()

        then:
        result.assertCurrentVersionHasNotRegressed()
    }

                }
            }
            dependencies {
                runtimeOnly project(":subproject")
            }
        """
        file("buildSrc/settings.gradle") << """
            include 'subproject'
        """
        buildFile << """
            apply plugin: MyPlugin
            apply plugin: MyPluginSub
            // nuke buildSrc classes so we can't use them

testing/internal-performance-testing/       @gradle/bt-developer-productivity
testing/internal-testing/                   @gradle/bt-developer-productivity

# Release coordination
subprojects/core-platform/              @gradle/bt-support
subprojects/distributions-dependencies/ @gradle/bt-support
subprojects/distributions-full/         @gradle/bt-support
testing/performance/                    @gradle/bt-support
testing/smoke-test/                     @gradle/bt-support

<%
    def i = 0
    def groups = subprojects.collect { "'$it'" }.groupBy { i++ % 100 }
    groups.each {
        println "include " + it.value.join(", ")
    }

        then:
        project.languageLevel.level == "JDK_1_5"
        project.jdkName == '1.6'
    }

    def "provides all modules"() {

        file('build.gradle').text = '''
subprojects {
    apply plugin: 'java'
}
'''
        file('settings.gradle').text = "include 'api', 'impl'"

        when:
        IdeaProject project = loadToolingModel(IdeaProject)

        then:

subprojects {
    apply from: rootProject.file("common.gradle")
    apply from: rootProject.file("components.gradle")
}

apply from: file("common.gradle")

link:../samples/sample_convention_plugins.html[**Convention plugins**] are plugins used to share build logic between subprojects (modules).
Users can wrap common logic in a convention plugin.
For example, a code coverage plugin used as a convention plugin can survey code coverage for the _entire project_ and _not_ just a specific subproject.

TIP: Gradle highly recommends the use of Convention plugins.

[.text-right]

Buildscript classes for Kotlin and Groovy are transformed via execution engine when they are compiled, base logic is in [BuildScriptCompileUnitOfWork.java](https://github.com/gradle/gradle/blob/master/subprojects/core/src/main/java/org/gradle/internal/scripts/BuildScriptCompileUnitOfWork.java)....

    repositories {
        mavenCentral()
    }
}
----

You can also include version catalogs in this section.

=== 5. Add subprojects to the build

The settings file defines the structure of the project by adding all the subprojects using the link:{javadocPath}/org/gradle/api/initialization/Settings.html[`include`] statement:

[source,kotlin]
----
include("app")
include("business-logic")