text(
            "additional.gradle.parameters",
            "",
            display = ParameterDisplay.NORMAL,
            allowEmpty = true,
            description = "The extra gradle parameters you want to pass to this build, e.g. `-PrerunAllTests` or `--no-build-cache`"
        )
        text(
            "reverse.dep.*.additional.gradle.parameters",
            "",

    * There is no way to opt-in an individual pod, with `sidecar.istio.io/inject`, without enabling injection
      for the entire namespace.

    These limitations have both been resolved. As a result, additional pods may be injected that were not in previous versions,
    if they exist in a namespace without an `istio-injection` label set but have the `sidecar.istio.io/inject` label set on the pod.

commands: [{
    executable: gradle
    args: check
    expected-output-file: checkTask.out
    allow-additional-output: true
    allow-disordered-output: true

  annotations: {}

  # Additional volumeMounts to the ztunnel container
  volumeMounts: []

  # Additional volumes to the ztunnel pod
  volumes: []

  # Annotations added to each pod. The default annotations are required for scraping prometheus (in most environments).
  podAnnotations:
    prometheus.io/port: "15020"
    prometheus.io/scrape: "true"

  # Additional labels to apply on the pod level
  podLabels: {}

# tag::cli[]
# gradle model
# end::cli[]
executable: gradle
args: model
expected-output-file: basicRuleSourcePlugin-model-task.out

====
include::sample[dir="kotlin",files="application/build.gradle.kts[]"]
include::sample[dir="groovy",files="application/build.gradle[]"]
====

The `application` project requires no additional configuration if the `jvm-test-suite` plugin is present.

<1> Apply the `test-report-aggregation` plugin
<2> Optional: make aggregate test report generation part of the 'check' lifecycle phase

# tag::cli[]
# gradle build
# end::cli[]
executable: gradle
args: build -q
expected-output-file: propertyGroovy.out
allow-additional-output: true

  <modelVersion>4.0.0</modelVersion>
  <groupId>org.apache.maven.lifecycle.test</groupId>
  <artifactId>project-with-additional-lifecycle-elements</artifactId>
  <packaging>jar</packaging>
  <version>1.0</version>
  <name>project-with-additional-lifecycle-elements</name>
  <url>http://maven.apache.org</url>

  <build>
    <pluginManagement>
      <plugins>
        <plugin>

sample inside an IDE using the https://www.jetbrains.com/help/idea/gradle.html#gradle_import_project_start[IntelliJ native importer] or https://projects.eclipse.org/projects/tools.buildship[Eclipse Buildship].

This sample shows how to add additional test types to a JVM project in Gradle. Your project may have many different kinds of tests--unit tests, integration tests, functional tests, etc. A JVM project in Gradle has a single `Test` task, but other tasks can be added to represent each of...

}

// SetCrashOutput configures a single additional file where unhandled
// panics and other fatal errors are printed, in addition to standard error.
// There is only one additional file: calling SetCrashOutput again overrides
// any earlier call.
// SetCrashOutput duplicates f's file descriptor, so the caller may safely
// close f as soon as SetCrashOutput returns.
// To disable this additional crash output, call SetCrashOutput(nil).