What's supported by Harness CI
Platforms and technologies 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 CI supported platforms and technologies
Harness CI supports a variety of platforms, repos, registries, and related technologies. The following sections list entities or providers with first-class support in Harness CI. Additional entities or providers may be supported through unofficial plugins or scripting.
Source Code Management (SCM)
In addition to built-in codebase cloning and support for Git functionality like Git LFS, subdirectory cloning, and PR status checks, Harness CI supports these SCM providers:
Other Git providers through the provider-agnostic Git connector
Build infrastructure
Harness CI offers Harness-managed and self-managed build infrastructure options for a variety of operating systems and architectures, including:
Harness CI Cloud (built in, Harness-managed, Linux/Windows/macOS) — supports Bring Your Own Image (BYOI) for custom VM images
Local runners (Linux/Windows/macOS)
Amazon Elastic Kubernetes Service (Amazon EKS)
Google Kubernetes Engine (GKE)
Red Hat OpenShift 4
Other, platform agnostic
Microsoft Azure (Linux/Windows)
GCP (Linux/Windows)
AWS EC2 (Linux/Windows)
AWS EC2 (macOS) - Harness recommends Harness CI Cloud for macOS builds due to licensing requirements and the complexity of managing macOS VMs with Anka virtualization.
Container registries
Azure Container Registry (ACR)
Amazon Elastic Container Registry (ECR)
Google Artifact Registry (GAR)
Google Container Registry (GCR) (pending deprecation)
Docker-compliant registries, such as Docker Hub, GitHub Container Registry (GHCR), and JFrog Docker registries
Other
For more information, go to Build and push artifacts and images.
Artifact repositories
JFrog Artifactory
AWS S3
GCP GCS
Sonatype Nexus
Other
For more information, go to Build and push artifacts and images.
Dependencies and caching
Harness CI supports running dependent services, such as Docker-in-Docker, LocalStack, and PostgreSQL, in Background steps.
Harness offers several caching options, including:
Harness Cache Intelligence
AWS S3
GCP GCS
Azure storage
Testing frameworks
Harness CI supports popular testing frameworks, including:
Bazel
CTest
Cucumber
DOTNET CLI
Go
Gradle
JUnit
Maven
Minitest
Mocha
NUnit
PHPUnit
Pytest
RSpec
Sbt
Unittest
Other
In addition to supporting various test types and tools, Harness CI also supports time saving and quality control functionality like test selection, code coverage, and test splitting. For more information, go to Run tests in CI pipelines.
Harness CI features
For an overview of key CI features, go to Harness CI overview and Harness CI key concepts.
For information about upcoming and recently released features, go to the CI product roadmap and CI release notes.
Harness CI early access features
Harness releases some CI features behind feature flags to get feedback from a subset of customers before making them generally available.
You can opt in to the early access (beta) features for Harness CI described in the following table. Contact Harness Support to enable specific early access features in your Harness account. Include the feature flag or name with your request.
CI_ENABLE_OUTPUT_SECRETS
Type selection for output variables in Run steps.
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 with self-managed VM build infrastructure.
Beta
CI_CODEBASE_SELECTOR
Delegate selectors for codebase tasks (CI-9980). Without this feature flag enabled, delegate selectors are not applied to delegate-related CI codebase tasks. With this feature flag enabled, Harness uses your delegate selectors for delegate-related codebase tasks. Harness prioritizes pipeline selectors over connector selectors for these tasks.
Beta
CI_OUTPUT_VARIABLES_AS_ENV
Output variables automatically become environment variables (CI-7817, ZD-39203).
With this feature flag enabled, Harness automatically makes step output variables available as environment variables for other steps in the same Build (CI) stage. For a Build stage with three steps, Harness makes an output variable from step one available to 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, you can later reference an output variable called MY_VAR as $MY_VAR. Without this feature flag enabled, you must use an expression 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.
Beta
CI_REMOTE_DEBUG
Remote debugging (CI-8135, CI-8048)
Harness CI supports remote debugging in certain scenarios. You can rerun builds in debug mode through the Builds, Execution, and Execution History pages in the Harness UI. Go to Debug mode for more information.
Debug mode supports Python, PowerShell Core (pwsh), and debugging in local runner build infrastructures. Debug mode is not supported in the Self-Managed Enterprise Edition. Go to Debug with SSH for more information.
Beta
CI_INCREASE_DEFAULT_RESOURCES
Used to adjust resource allocation 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. 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 do not 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
Speeds up CI builds by adding more resources for the addon.
Beta
CI_OVERRIDE_SERVICE_URLS
This flag overrides all Harness service URLs (for example, TI Service and Log Service). These URLs are derived from the manager URL.
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 always return successful results and bypass 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. Go to Create a connector using YAML for more information.
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
Last updated
Was this helpful?