### Extensibility platform

This is a platform that builds on the core, software and JVM platforms to add support for extending Gradle by implementing and applying plugins.

This platform includes the plugin publishing plugin and the plugin portal.

### Native platform

This is a platform that builds on the core and software platforms to add support for developing native software.

on:
  - pr_created
  - commit
  - comment_added

automations:

  summary_table_platforms:
    if:
      - {{ ('summary_table_platforms' | isEnabledAutomation(pr)) }}
    run:
      - action: add-comment@v1
        args:
          comment: |
            {{ by_platform_comment }}

by_platform_comment: |

# JVM platform
platforms/jvm/                              @gradle/bt-jvm
subprojects/plugins/                        @gradle/bt-jvm

# JVM testing services also shared by GE testing plugins
platforms/jvm/testing-junit-platform/       @gradle/bt-jvm @gradle/ge-testing
platforms/jvm/testing-jvm/                  @gradle/bt-jvm @gradle/ge-testing
platforms/jvm/testing-jvm-infrastructure/   @gradle/bt-jvm @gradle/ge-testing

# Software platform

## Platform architecture

Gradle is arranged into several coarse-grained components called "platforms".
Each platform provides support for some kind of automation, such as building JVM software or building Gradle plugins.
Most platforms typically build on the features of other platforms.

  {
    "name": "java-platform",
    "path": "platforms/jvm/java-platform",
    "unitTests": true,
    "functionalTests": true,
    "crossVersionTests": false
  },
  {
    "name": "jvm-services",
    "path": "platforms/jvm/jvm-services",
    "unitTests": true,
    "functionalTests": true,
    "crossVersionTests": false
  },
  {
    "name": "kotlin-dsl",
    "path": "platforms/core-configuration/kotlin-dsl",

 * @description Returns a mapping of platforms to the information about the files involved in the PR contained in each platform
 * @param {Map} fileOwners mapping of platform name to a list of files involved in the change located in that platform
 * @param {[FileMetadata]} fileMetadatas - gitStream's list of metadata about file changes in the PR including path

# The `name:` field specifies the platform label, e.g. `name: build_infrastructure` => `platform:build_infrastructure` label
platforms:
  - bt_ge_build_cache:
    name: 'bt_ge_build_cache'
    subprojects:
      - 'platforms/core-execution/build-cache/'
      - 'platforms/core-execution/build-cache-base/'
      - 'platforms/core-execution/build-cache-http/'
      - 'platforms/core-execution/build-cache-packaging/'

    private static final List<String> MONITORED_FILES = [
        "subprojects/docs/src/docs/release/notes.md",
        "platforms/documentation/docs/src/docs/release/notes.md",
        "subprojects/launcher/src/main/resources/release-features.txt",
        "platforms/core-runtime/launcher/src/main/resources/release-features.txt"
    ]

    static void main(String[] commits) {

    let result = "";
    if (statistics.length > 1) {
        result += statistics.length + " platforms were affected";
    } else {
        result += "1 platform was affected";
    }
    if (platformsWithSignificantChanges.length > 1) {
        result += " (:warning: if possible, only one platform should have significant changes in a PR)";
    } else {
        result += " ";
    }
    return result;
}

  - pr_created
  - commit
  - comment_added

automations:

  # Label changes by affected platforms (in blue)
  {% for platform in platforms %}
  platform_label_{{ platform.name }}:
    if:
      - {{ ('platform_labels' | isEnabledAutomation(pr)) }}
      - {{ files | byPlatform | categorize(branch.diff.files_metadata) | readField(platform.name, 'files') | nullToEmpty | some }}
    run:
      - action: add-label@v1
        args: