Feature Requests

plugins/cache plugins/sto plugins/s3

Currently, when we run tests using TI in Harness, the tests tab doesn't display which split classes are being used for running which tests. Due to this, it is difficult to understand and obtain information about the tests with split classes. Adding this field will help in debugging issues with respect to test selection further.

Make mobile builds faster by supporting Xcode in Build and Cache Intelligence

Currently, each pipeline run pulls large custom Windows images (~8GB) from ECR, which introduces considerable overhead and slows down builds. Improvements that would help: Persistent image caching across builds on Harness Cloud runners Docker Layer Caching support for Windows containers Option to preload frequently used custom images in Harness-managed warm pool VMs Registry mirroring or caching to reduce pull latency These enhancements would significantly improve pipeline performance and deliver a better developer experience.

We have security enforcement on our Openshift platform that refuse the image with user ContainerAdministrator. We need a rootless (UserContainer) for the plugins/cache image. This will provide a cache for DotNet 4.8 (which must be compiled under Windows) and gain developer buy-in through a better development experience.

We ideally need secure mode communication between the harness delegate and the windows local runner service as I understand the service can be configured to support TLS connections however the harness delegate has no way to pass the required certs so communication fails, can this be delivered?

Docker images (where they don't contain IP) utilized by the Harness platform should be open to extension and allow the users to customize behaviors

The UI for exposing input elements of container builds is much easier and cleaner than using plugin steps as you can't present out a multi input option like build arguments. We need to use Buildah as we need a non privileged build capability. We'd like buildah to be a supported option in the build steps. Also you should be able to select the "engine" from a drop down to be able to use say Kaniko in one step and Buildah in another.

Followup for support ticket: https://support.harness.io/hc/en-us/requests/83311 I'd like to be able to write conditional execution/control execution based on the status of the cache intelligence step. I cannot use expressions for these steps because their identifiers have hyphens in them.

Feature request as suggest by Harness team to enable system level error retry mechanism for the below failures : - Pod eviction Failure to connect to addon client Connectivity errors between delegate and ci lite engine ref : https://support.harness.io/hc/en-us/requests/72479?page=1