### 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.

# 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",

  - 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:

## Composition by architecture modules

Each [architecture module and platform](platforms.md) can contribute code to any of the runtimes.
Not every module contributes to every runtime.

The core-runtime module defines each runtime:

        }
        result.get(platform).push(file);
    });

    console.log("byPlatform: ");
    [...result.keys()].forEach(platform => {
        console.log("[" + platform + ": [" + result.get(platform).join(", ") + "]]");
    });
    return result;
}

function getPlatform(file) {
    let result = null; // Default to null in case no platform is found

    if (file.startsWith('platforms/')) {

* Add documentation to the User Manual and DSL Reference (under [platforms/documentation/docs/src/docs](platforms/documentation/docs/src/docs/)).
* For new features, the feature should be mentioned in the [Release Notes](platforms/documentation/docs/src/docs/release/notes.md).

build:rbe_linux_cpu --extra_execution_platforms="@sigbuild-r2.17-clang_config_platform//:platform"
build:rbe_linux_cpu --host_platform="@sigbuild-r2.17-clang_config_platform//:platform"
build:rbe_linux_cpu --platforms="@sigbuild-r2.17-clang_config_platform//:platform"
# This is needed for all Clang17 builds but must not be present in GCC builds.

// along with this program.  If not, see <http://www.gnu.org/licenses/>.

package http

import (
	"context"
	"net"
	"syscall"
	"time"
)

// TODO: if possible implement for non-linux platforms, not a priority at the moment
//
//nolint:unused
func setTCPParametersFn(opts TCPOptions) func(network, address string, c syscall.RawConn) error {
	return func(network, address string, c syscall.RawConn) error {
		return nil