> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/continuous-integration/3.0/troubleshooting-and-resources/ci-supported-platforms.md).
# What's supported by Harness CI
This page describes supported platforms and technologies for Harness CI specifically.
For information about what's supported for other Harness modules and the Harness Platform overall, go to [Supported platforms and technologies](/harness-ai/new-to-harness-platform/platform-whats-supported.md).
### Harness CI supported platforms and technologies
### Harness CI features
For an overview of key CI features, go to [Harness CI overview](/continuous-integration/3.0/new-to-harness-ci/overview.md) and [Harness CI key concepts](/continuous-integration/3.0/new-to-harness-ci/key-concepts.md).
For information about upcoming and recently released features, go to the [CI product roadmap](https://developer.harness.io/roadmap/#ci), [CI release notes](/release-notes/continuous-integration.md).
#### Harness CI early access features
Some Harness CI features are released behind feature flags to get feedback from a subset of customers before releasing the features to general availability.
You can opt-in to the early access (beta) features for Harness CI described in the following table. Contact [Harness Support](mailto:support@harness.io) to enable specific early access features in your Harness account. Include the feature flag or name with your request.
| Flag | Description | Availability |
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------ |
| `CI_ENABLE_OUTPUT_SECRETS` | Type selection for [output variables in Run steps](/continuous-integration/3.0/use-harness-ci/use-harness-ci/run-step-settings.md#output-variables). | Beta |
| `CI_USE_LESS_STRICT_EVALUATION_FOR_MAP_VARS` | Allows empty environment variables in CI pipelines. | Beta |
| `CI_USE_LESS_STRICT_EVALUATION_FOR_MAP_VARS` | Allows empty environment variables in CI pipelines. | Beta |
| `CI_ENABLE_VM_DELEGATE_SELECTOR` | Delegate selectors for self-managed VM build infrastructures (CI-11545). | |
| With this feature flag enabled, you can use [delegate selectors](/harness-ai/use-harness-platform/delegates/delegate/manage-delegates/select-delegates-with-selectors.md) with [self-managed VM build infrastructure](/continuous-integration/3.0/use-harness-ci/use-harness-ci/set-up-build-infrastructure/vm-build-infrastructure.md). | Beta | |
| `CI_CODEBASE_SELECTOR` | Delegate selectors for codebase tasks (CI-9980). | |
| Without this feature flag enabled, delegate selectors aren't applied to delegate-related CI codebase tasks. | | |
| With this feature flag enabled, Harness uses your [delegate selectors](/harness-ai/use-harness-platform/delegates/delegate/manage-delegates/select-delegates-with-selectors.md) for delegate-related codebase tasks. Delegate selection for these tasks takes precedence in order of [pipeline selectors](/harness-ai/use-harness-platform/delegates/delegate/manage-delegates/select-delegates-with-selectors.md#pipeline-delegate-selector) over [connector selectors](/harness-ai/use-harness-platform/delegates/delegate/manage-delegates/select-delegates-with-selectors.md#infrastructure-connector). | Beta | |
| `CI_OUTPUT_VARIABLES_AS_ENV` | Output variables automatically become environment variables (CI-7817, ZD-39203). | |
| With this feature flag enabled, output variables from steps are automatically available as environment variables for other steps in the same Build (`CI`) stage. This means that, if you have a Build stage with three steps, an output variable produced from step one is automatically available as an environment variable for steps two and three. | | |
| In other steps in the same stage, you can refer to the output variable by its key without additional identification. For example, an output variable called `MY_VAR` can be referenced later as simply `$MY_VAR`. Without this feature flag enabled, you must use an [expression](/harness-ai/use-harness-platform/variables-and-expressions/runtime-inputs.md#expressions) to reference where the variable originated, such as `<+steps.stepID.output.outputVariables.MY_VAR>`. | | |
| For more information on this feature, go to the documentation on [Output variables](/continuous-integration/3.0/use-harness-ci/use-harness-ci/run-step-settings.md#output-variables). | Beta | |
| `CI_REMOTE_DEBUG` | Remote debugging (CI-8135, CI-8048) | |
| Harness CI now supports remote debugging in certain scenarios. You can re-run builds in debug mode through the **Builds**, **Execution**, and **Execution History** pages of the Harness UI. For more information, go to [Debug mode](/continuous-integration/3.0/troubleshooting-and-resources/troubleshoot-harness-ci/debug-mode.md). | | |
| **Update (June 2023):** Debug mode now supports Python, PowerShell Core (`pwsh`), and debugging in local runner build infrastructures. Debug mode is not supported in the Self-Managed Enterprise Edition. For more information, go to [Debug with SSH](/continuous-integration/3.0/troubleshooting-and-resources/troubleshoot-harness-ci/debug-mode.md) | Beta | |
| `CI_INCREASE_DEFAULT_RESOURCES` | Used to adjust [resource allocation limits](/continuous-integration/3.0/use-harness-ci/use-harness-ci/set-up-build-infrastructure/resource-limits.md#override-resource-limits). This feature flag increases maximum CPU to 1000m and maximum memory to 3000Mi. | Beta |
| `CI_CONSERVATIVE_K8_RESOURCE_LIMITS` | Used to adjust [resource allocation limits](/continuous-integration/3.0/use-harness-ci/use-harness-ci/set-up-build-infrastructure/resource-limits.md#override-resource-limits). This feature flag sets lite engine resource limits to the default minimum (100m CPU and 100Mi memory). | Beta |
| `CI_REMOVE_FQN_DEPENDENCY` | This flag is useful for steps that use a private Docker registry. With this flag enabled, the step uses the URI specified in the Docker connector. This means you don't need to specify the Fully Qualified Name in the Image field. This change applies to the following steps: **Plugin**, **Background**, **Run**, **Run Tests**, and **Test Intelligence**. | Beta |
| `CI_EXTRA_ADDON_RESOURCE` | Used to speed up CI builds by adding more resources for running 'addon\`. | Beta |
| `CI_OVERRIDE_SERVICE_URLS` | Using this flag overrides all Harness service URLs (e.g. TI Service, Log Service, etc.). These URLs will be derived from the [manager URL](/harness-ai/use-harness-platform/delegates/delegate/delegate-reference/delegate-environment-variables.md#manager_host_and_port) | Beta |
| `CI_POPULATE_CI_VARIABLE` | Enforces that the environment variable `CI` is always `true` for all builds. | Beta |
| `CI_IGNORE_TEST_CONNECTION` | Skip connector preflight checks (CI-13806). | |
| When this account-level feature flag is enabled along with the `ignoreTestConnection: true` property in a connector's YAML configuration, connection tests will always return as successful, bypassing actual connectivity validation. This is useful when network restrictions, split DNS, or firewall policies prevent connection tests from succeeding even though the connector can function properly at runtime. For more information, go to [Create a connector using YAML](/harness-ai/use-harness-platform/connectors/create-a-connector-using-yaml.md). | Beta | |
| `CI_SCM_TASK_TIMEOUT_CONFIGURABLE` | Increase SCM codebase task timeout (CI-22015). | |
| Without this feature flag enabled, the SCM codebase task that fetches pull request, branch, or commit metadata uses a 30-second timeout. With this feature flag enabled, Harness uses a 180-second timeout for this task. Enable this flag for accounts with large pull requests or slow Git providers where the default 30-second timeout results in pipeline failures with the error `Failed to retrieve codebase info from returned delegate response`. | Beta | |