Feature Requests

Our firm's Docker Desktop team is requesting for Harness to change how it mounts to Docker Desktop. Instead of Harness mounting to the Docker Socket with all CI images, that it only mounts the images that is needed.

As of today, the drone-git support is available upto windows server 2022 and we are in a need to build the windows based docker image for 2025 hence we are requesting to support drone-git for windows server 2025.

On Windows EC2 build infrastructure, containers cannot reach the AWS metadata endpoint (169.254.169.254) because host networking is not supported, unlike Linux. As a result, built-in steps such as upload to S3 (configured with AWS connector with IRSA) fail when trying to assume IAM roles from within the container. We need an enhancement to allow Windows containers used by the built in steps to natively access the metadata/credentials endpoints or run the builtin steps directly on the VM instead of running inside another container, so that we can securely assume IAM roles.

Solution: Harness Proxy details has to be implicitly set as build args for Docker Build Plugin. Current Issue: Harness Proxy needs to be explicitly set as step output variables so that they can be set as build args for Docker Build Plugin export HTTPS_PROXY="$HARNESS_HTTPS_PROXY" export HTTP_PROXY="$HARNESS_HTTP_PROXY" export NO_PROXY="$HARNESS_NO_PROXY" This is a redundant repeatative obvious step which as an User, I do not need to add a step explicitily. Business Value: Users of the Docker Build Plugin step will have better experience and will add intelligence to the step

BuildX requires a buildkit.toml file to be included for certs. This does not get auto-generated by Harness so users will need to add extra steps in their pipeline to generate this file. We'd like for Harness to auto-generate this file based on the certificates we have mounted in the CI Pod.

Many reports such as coverage, linters, unit tests from various languages, etc use proprietary HTML reports. Harness enables you to upload these reports as artifacts to S3 or similar, but it does not support HTML reports natively. I would like to see this feature make it to Harness similar to https://plugins.jenkins.io/htmlpublisher/ to support additional quality and build reports

Prevent CI/CD infra throttling by enforcing global and partitioned concurrency limits, per-pipeline maxConcurrency, and queue-based guardrails so bulk triggers (for example, ~1000 parallel starts) are automatically queued instead of saturating shared runners, delegates, and clusters.

PIE_RESOLVE_EXECUTION_INPUT_EXPRESSION i need to get the feature enabled . Please let me know what details are required

i need the feature enabled for us let me know what details will be required for this PIE_RESOLVE_EXECUTION_INPUT_EXPRESSION

We are currently working on CI/CD automation for the EPM-ARCS application and would like to request a standard process or template for setting up a Harness CI job. Our current workflow involves: Using GitHub Enterprise (GHE) for source code management, where our application binaries (such as .zip and .iar files) are stored and managed. Running Nexus IQ scans on these artifacts. Pushing the scanned artifacts to the SAR repository for deployment. Could you please assist us with a standardised process or provide a reusable template that aligns with this setup? If any further information is required, please let me know. Thanks & Regards, Bapujee U