Feature Requests

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

Currently the step logs are getting truncated when it is exceeding a size of 5MB. The workaround suggested to save the script output to a file and make it available in an object store is not helpful and having issues using this workaround in the run test step. We should be able to see the full step logs even if it is exceeding the sizes of 5MB

I Would like to access service variables, and repository name from the service directly when doing CI stages Service would be the only entity for CI/CD

Currently the multiline string values are not supported with the CI run step output variable. We need to be able to use multiline string as the value for run step output variable

When a CI stage is present in a pipeline and it gets triggered by a trigger of type ARTIFACT the pipeline throws this error Invalid request: CI stage cannot be triggered by trigger of type: ARTIFACT

Similar to the CD module user would like to have the Approval as a CI step.

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

Feature request: Need the ability to dynamically set environment variables for a step, or parse from JSON. This will enable more flexible use of in-stage builders and lessen inputs only needed for certain use cases.

While clicking the run pipeline we dont get option to select a branch instead a text box to enter the branch name which is not user friendly. Would be great if we can get a drop down of all branches which we can select from.

We would like to have the default container resources (Limit Memory – 500Mi & Limit CPU – 400m) removed so that there would be no limit set at all. Either removing it from your side works or even preferrable to give this control to us to set / remove the default limits, especially when we're relying on self-hosted build infra i.e in our case our on-prem k8s cluster. This helps us address the resource issues across the account, instead of customizing the resources specific to individual pipelines/steps which would be an overhead and also not reliable. We understand there is a FF to increase the defaults but we're not looking at that option, we're looking to have the defaults removed or the control be given to us. When we're leveraging our self-hosted build infra, we expect to have that control.