fun asConfigurationId(
        model: CIBuildModel,
        subProject: String = "",
    ): String {
        val prefix = "${testCoveragePrefix}_"
        val shortenedSubprojectName = shortenSubprojectName(model.projectId, prefix + subProject)
        return model.projectId + "_" + if (subProject.isNotEmpty()) shortenedSubprojectName else "${prefix}0"
    }

    private fun shortenSubprojectName(

            subProject(stageProject)

            prevStage = stage
            previousPerformanceTestPasses.addAll(stageProject.performanceTests)
            previousCrossVersionTests.addAll(stageProject.crossVersionTests)
        }

        buildType(GitHubMergeQueueCheckPass(model))

        buildTypesOrder = buildTypes
        subProjectsOrder = subProjects

        cleanupRule(

  - Suppose the VCS root you just create is `MyNewVcsRoot`. Set "default branch" to `myTestBranch` where your code exists.
- Click `Create subproject` button at the bottom of the "Subprojects" region of [this page](https://builds.gradle.org/admin/editProject.html?projectId=Gradle&tab=projectGeneralTab)
  - Select `Manually`.

                    FunctionalTestBucket(it).toBuildTypeBucket(model.subprojects)
                }

            // Sometimes people may add new subproject into `subprojects.json`
            // in this case we have no historical test running time, so we simply add these subprojects into first available bucket
            val allSubprojectsInBucketJson = buckets.flatMap { it.subprojects.map { it.name } }.toSet()

            val allSubprojectsInModel =

        val currentCommit = parameters.currentCommit.get()
        outputFile.parentFile.mkdirs()
        outputFile.printWriter(Charsets.UTF_8).use { writer ->
            writer.println("Link;Platform/Subproject;Incubating since")
            data.toSortedMap().forEach { (category, projectsWithProblems) ->
                projectsWithProblems.forEach { (project, problems) ->
                    problems.forEach {

### Testing changes

After making changes, you can test your code in 2 ways:

#### Run tests

- Run `./gradlew :<subproject>:quickTest` where `<subproject>` is the name of the subproject you've changed. 
- For example: `./gradlew :launcher:quickTest`.

#### Install Gradle locally

and try out a change in behavior manually. 

        get() = localRepo.asFileTree.matching {
            include("**/*.jar")
            // https://github.com/gradle/gradle-private/issues/4253
            // Only a few tests need the sources jar in tooling-api subproject
            if (projectName != "tooling-api") {
                exclude("**/*-sources.jar")
            }
            exclude("**/*-javadoc.jar")
        }.files.toSortedSet()

    /**

    <!-- We like it explicit -->
    <suppress checks="ExplicitInitializationCheck"
              files=".*"/>

    <!-- Ignore code from maven subproject under org.apache -->
    <suppress checks="RegexpSingleline"
              files=".*[/\\]maven[/\\]src[/\\]main[/\\]java[/\\]org[/\\]apache[/\\].+"/>
    <suppress checks="RegexpHeader"

 * called the <dfn>aggregator project</dfn> lists one or more <dfn>sub-projects</dfn>
 * which are relative pointers on the file system to other projects. This is done using
 * the {@code /project/subprojects/subproject} elements of the POM in the aggregator project.
 * Note that the aggregator project is required to have a {@code pom} packaging.</p>
 *

            Element subprojects = DomUtils.findChildElement(root, "subprojects");
            assertNotNull(subprojects);

            // Verify module elements were renamed to subproject
            var moduleElements = subprojects.children("module").toList();
            var subprojectElements = subprojects.children("subproject").toList();
            assertEquals(0, moduleElements.size());