into("build/distro")
            }
        """
        when:

        def result = gradleRunner("setupDistro").build()
        then:
        result.task(":distribution:bwc:minor:buildBwcExpandedTask").outcome == TaskOutcome.SUCCESS
        result.task(":setupDistro").outcome == TaskOutcome.SUCCESS
        assertExtractedDistroIsCreated("distribution/bwc/minor/build/install/elastic-distro",

                    <version>1.0.0</version>
                    <build>
                        <plugins>
                            <plugin>
                                <artifactId>maven-shade-plugin</artifactId>
                                <version>3.1.0</version>
                            </plugin>
                        </plugins>
                    </build>
                </project>
                """;

        <skip implementation="boolean" default-value="false">${remoteresources.skip}</skip>
        <outputDirectory implementation="java.io.File">${project.build.directory}/maven-shared-archive-resources</outputDirectory>
        <excludeArtifactIds implementation="java.lang.String" default-value="">${excludeArtifactIds}</excludeArtifactIds>

  <modelVersion>4.1.0</modelVersion>

  <properties>
    <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
    <project.reporting.outputEncoding>UTF-8</project.reporting.outputEncoding>
    <!-- Fixed date for reproducible build -->
    <project.build.outputTimestamp>1980-02-01T00:00:00Z</project.build.outputTimestamp>
  </properties>

  <build>
    <directory>${project.basedir}/target</directory>

Some requests will require that the build is configured and maybe some work executed, and other requests might not.

See [Build execution model](build-execution-model.md) for more details.

### Build state model

As Gradle executes, it acts on various pieces of the build definition, such as each project in the build.

            step.gradleParams,
        )
    }

    @Test
    fun `start release cycle test promotion build type runs one gradle invocation`() {

/backwards
/dev-tools/backwards

# needed in case docs build is run...maybe we can configure doc build to generate files under build?
html_docs

# random old stuff that we should look at the necessity of...
/tmp/
eclipse-build

# projects using testfixtures
testfixtures_shared/

# These are generated from .ci/jobs.t, .ci/templates.t and .ci/views.t
.ci/jobs/
.ci/templates/
.ci/views/

  @Test
  public void nodeOrder_none() {
    MutableGraph<Integer> graph = GraphBuilder.directed().nodeOrder(unordered()).build();

    assertThat(graph.nodeOrder()).isEqualTo(unordered());
  }

  @Test
  public void nodeOrder_insertion() {
    MutableGraph<Integer> graph = GraphBuilder.directed().nodeOrder(insertion()).build();

    addNodes(graph);

    assertThat(graph.nodeOrder()).isEqualTo(insertion());

            "failed-report-with-leftover/build/tmp/teŝt files",
            "successful-report/build/tmp/teŝt files",
            "failed-test-with-leftover/build/tmp/teŝt files"
        )
    }

    @Test
    fun `build does not fail if a flaky test has leftover files`() {
        val result = run(":flaky-test-with-leftover:test").build()

    }

    @Test
    void testTargetPath() {
        Build build = mock(Build.class);
        when(build.getDirectory()).thenReturn("target");
        when(build.getOutputDirectory()).thenReturn("target/classes");
        when(build.getTestOutputDirectory()).thenReturn("target/test-classes");

        Project project = mock(Project.class);
        when(project.getBuild()).thenReturn(build);