manifest:
  version: 1.0

# The `automations` section lists automations to run on PRs in this repository.
# Each automation has an `if` key that defines conditions to run the automation,
# as well as a `run` key with the actions to do. All the conditions need to be true
# for the actions to run (there is an implicit AND relation between
# the conditions on each line).  Each condition is specified as a Jinja expression.  You

  # Enable debug for the `gradle-build-action` cache operations
  GRADLE_BUILD_ACTION_CACHE_DEBUG_ENABLED: true

permissions: {}

jobs:
  build:
    name: "Compile All"
    permissions:
      contents: read
    runs-on: ubuntu-latest
    steps:
      - name: git clone
        uses: actions/checkout@v4
      - id: setup-matrix

            }
        }
    }

    private void addAnchorsForHeadings(Document document) {
        // add anchors for all of the headings
        for (Element heading : document.body().select("h2,h3,h4")) {
            String anchorName = heading.text().toLowerCase().replaceAll(" ", "-");
            heading.attr("id", anchorName);
        }

 * See the License for the specific language governing permissions and
 * limitations under the License.
 */

package common

import common.KillProcessMode.KILL_ALL_GRADLE_PROCESSES
import configurations.CompileAll
import configurations.FunctionalTest
import configurations.branchesFilterExcluding
import configurations.buildScanCustomValue
import configurations.buildScanTag

/**
 * @module computeStatistics
 * @description Summarizes the changes to files in the PR by platform.
 *
 * @param {Map} groupedFiles - map of platforms for containing info about the changes to files in that platform, from call to categorize
 * @param {[FileMetadata]} fileMetadatas - gitStream's list of metadata about file changes in the PR including path
 * @returns {[Object]} Returns list of computed summary statistic objects for each platform in the input groupedFiles

 * @description Returns true if the given automation should run against the given PR.
 *
 * This is determined by checking if any of the following conditions are met:
 *
 * <ul>
 *     <li>The automation is enabled for all PRs via the presence of 'always' in the appropriate map entry above.</li>
 * </ul>
 *
 * or
 *
 * <ul>
 *     <li>The author is a member of the Gradle organization,</li>

          days-before-issue-stale: 14
          stale-issue-label: to-triage
          stale-issue-message: ""
          days-before-issue-close: -1

          only-pr-labels: 'from:contributor'
          exempt-all-pr-milestones: true
          days-before-pr-stale: 14
          stale-pr-label: to-triage
          stale-pr-message: ""

  build2 --> project3
  
  project4["project"]
  build2 --> project4

```

### Build process state

The "build process state" holds the global state of the build process and manages all the other state.

The build process state also includes state that is tied to a particular Gradle user home directory.
When that directory changes between Gradle invocations, the state is discarded and recreated.

    val testNameParameterName = "testName"
    val testTaskOptionsParameterName = "testTaskOptions"
    val daemon = true
    applyDefaultSettings(os, arch, buildJvm = BuildToolBuildJvm, timeout = 0)

    // Show all failed tests here, since that is what we are interested in
    failureConditions.supportTestRetry = false

    "linux" : 398
  }, {
    "testProject" : "largeMonolithicJavaProject",
    "linux" : 194
  } ]
}, {
  "scenario" : "org.gradle.performance.regression.java.JavaTasksPerformanceTest.tasks --all",
  "durations" : [ {
    "testProject" : "largeJavaMultiProject",
    "linux" : 426
  }, {
    "testProject" : "largeMonolithicJavaProject",
    "linux" : 183
  } ]
}, {