Feature Requests

Harness is used to run tests on PR. If it fails then I can't merge my PR. Often, Harness fails to clone the codebase where the tests are located. Entire check fails and I need to manually rerun it. Please retry failed git clone operations so we don't need to rerun them manually!

you can find details on the ticket - https://support.harness.io/hc/en-us/requests/81863 we need to run our cobol build on a server, we installed docker delegate and docker harness runner. when we execute pipeline we are getting below error failed with code: 500, message: { "error_msg": "failed to create directory for host volume path: /addon: mkdir /addon: permission denied" } . we cannot use root user for any app builds on our server. We need to have delegate to run as non root user

According to https://developer.harness.io/docs/continuous-integration/use-ci/caching-ci-data/cache-intelligence/#enable-cache-intelligence you only support WORKSPACE for Bazel builds. Can we support the new MODULE.bazel which was introduced at Bazel 6.0 December 2022? WORKSPACE is legacy now. see - https://bazel.build/external/migration

We need to update specific labels/annotations in the delegate. The values are not exposed via the value file: https://github.com/harness/delegate-helm-chart/blob/1392fd3ac5c6334db529f06554fbbe6fdc4f0146/harness-delegate-ng/templates/_helpers.tpl#L44-L48 We need another setting in the values.yaml file so we can add to those tags. We are trying to add the labels and annotations shown here: https://app.datadoghq.com/apm/service-setup?architecture=container-based&collection=Helm%20Chart%20%28Recommended%29&environment=kubernetes&language=java

The ability to leverage Github Actions directly in Harness is a HUGE accelerator. Currently they are only supported in Cloud infrastructure due to the pre-requisites needed to be installed on the VM. These should be made available for self-managed VM build infrastructure as well, assuming the pre-requisites are published and can be installed and setup on the VM.

I need a feature that allows us to control who can use account-level delegates in specific projects without having to explicitly grant permissions. This would help in managing access more efficiently and prevent unauthorized usage of delegates.

in build https://app.harness.io/ng/account/Q8_q5d7BQy-0iAh0D8klTw/module/ci/orgs/default/projects/anywhere/pipelines/AWS_Main_Pipeline/executions/ERe3GDQ3R0KhEfwdQlx_-w/pipeline?stage=WEL33PwXQsWykIjLQXCRaQ we just had a failure: fatal: could not read Password for 'https://ghp_xyz32gewwhrtiohwrtpopwttiet@github.com': No such device or address Prefferably, TOKEN should not be shown.

Currently Harness STO module does not have option for ORCA integration for vulnerability scan. Raising this enhancement request to support this integration.

The image size of plugins/artifactory:1.7.1 was around 1.78 GB, which included the JFrog CLI packages. We’ve recently added support for jfrog-mvn and jfrog-gradle, and to enable that, both Maven and Gradle packages were bundled inside the container. As a result, the Windows variant of the image now weighs around 2.32 GB. Even with version 1.7.1, the image size was already close to 2 GB. On using the latest Artifactory plugin image, I consistently observe 4–6 minutes of pull time on Harness Cloud. We want this image size to be reduced/optimised so that the download time can be reduced on the infra.

It would be really nice to be able to explicitly raise a specific type of error from a shell script, so that the script author can influence the failure strategy as a result of the script execution. Even better, it would be really create to be able to create custom error types that can then branch rollback logic It could be as simple as tying error types to specific shell script exit codes, and having a UI for creating error types where you can specify the exit code to associate with it