"build-profile"
				]
			},
			{
				"parallelizationMethod":{
					"name":"TestDistribution"
				},
				"subprojects":[
					"scala",
					"plugins-java-base",
					"problems-api",
					"problems",
					"build-cache",
					"build-configuration",
					"declarative-dsl-core",
					"plugins-test-report-aggregation",
					"testing-base",
					"tooling-native",
					"java-platform"
				]

That meant possible solutions for Problems could be scattered all over the console output.
To improve the user experience, we introduced a new way to provide suggestions.
The idea is to provide a list of suggestions for a problem in the console output.
The suggestions are displayed in the separate "Try"- section of the console output.

name: Regression
description: Report a problem about something that used to work
labels: [ "a:regression", "to-triage" ]
assignees: [ ]
body:
  - type: markdown
    attributes:
      value: |
        Please use our bug report template to report problems with something that has never worked.
        Regressions reports are greatly appreciated during our RC phase and before a final release.
  - type: textarea
    id: current-behavior
    attributes:

import java.io.Serializable
import java.util.concurrent.CopyOnWriteArrayList

/**
 * Register a build service that monitors compilation tasks and code quality tasks (Checkstyle/CodeNarc/ktlint)
 * and reports them as TeamCity build problems.
 */
registerBuildScanInfoCollectingService(CollectFailedTaskPathsBuildService::class.java, ::shouldBeReportedAsTeamCityBuildProblem) { failedTasksInBuildLogic, failedTasksInMainBuild ->
    buildScanPublished {

# IDE Experience team
platforms/ide/                    @gradle/bt-ide-experience
# Eventually be moved to the core platform.
# Currently heavily developed by the bt-ide-experience team.
platforms/ide/problems/           @gradle/bt-ide-experience
platforms/ide/ide-native/         @gradle/bt-ide-experience @gradle/bt-native-maintainers

# Documentation

            display = ParameterDisplay.PROMPT,
            allowEmpty = false,
            description = "The name of the test to run, as should be passed to --tests. Can't contain spaces since there are problems with Teamcity's escaping, you can use * instead."
        )
        text(
            testJvmVersionParameter,
            JvmVersion.java11.major.toString(),
            display = ParameterDisplay.PROMPT,

## Decision

Introduce a "UI" architecture module to the core platform, and move the user interaction services to this new module.

This includes:

- Logging and progress services.
- Problem generation services (aka the "problems API").
- User prompting services.
- Build options infrastructure.
- The console and CLI, as a specific implementation of these services.

    "functionalTests": true,
    "crossVersionTests": true
  },
  {
    "name": "problems",
    "path": "platforms/ide/problems",
    "unitTests": false,
    "functionalTests": true,
    "crossVersionTests": false
  },
  {
    "name": "problems-api",
    "path": "platforms/ide/problems-api",
    "unitTests": true,
    "functionalTests": true,
    "crossVersionTests": false
  },
  {

            // in this case we need to explicitly configure the PTS server
            // Don't move this line into the lambda as it may cause config cache problems
            extensions.findByType<PredictiveTestSelectionExtension>()?.apply {
                this as PredictiveTestSelectionExtensionInternal
                server = uri("https://ge.gradle.org")

To disable the configuration cache, run the build with `--no-configuration-cache`.

Tasks known to have problems are listed in the build logic. You can find this list at:

    build-logic/root-build/src/main/kotlin/gradlebuild.internal.cc-experiment.gradle.kts