Feature Requests

We were going through this feature to visualize CPU and memory utilization metrics on Cloud builds: https://developer.harness.io/docs/continuous-integration/use-ci/set-up-build-infrastructure/view-resource-utilization-metrics/ Is there a plan to provide the same feature on self-managed build infrastructures? Any ETA for this feature?

Hello, we would like to be able to handle triggers in git experience same as pipelines and input sets. Currently everything but triggers is able to be maintained by git experience, leading to a situation where you think everything is managed in code, but it really is not and you are missing context as to how things work. This is especially true when onboarding new engineers onto Harness and causes unnecessary confusion. Thanks

Is there a way to freeze (prevent execution) of custom stages and CI stages as part of a freeze window? We have many pipelines which leverage these custom stages as part of deployments. Additionally, we sometimes need to freeze builds.

Please add the EMAIL step for the Build stage type. We are forced to use Custom or Deploy stage to be able to send an email. This is impacting to get metrics as we have jobs which monitor our services which need to use CUSTOM and in the metrics it is being marked as DEPLOYMENT in the deployment metrics but it is not deploying. So to avoid this, we want to move that logic to build so it won't show in the deployment metrics. User also checked the plugin email step for CI but they require native Email step support similar as CD.

Enable CI PR builds for Bitbucket forked repositories (external providers) Request Support CI pipeline execution for pull requests originating from Bitbucket forked repositories, even when: -The fork is owned by an external provider. -The base repository is defined as the pipeline’s codebase. Harness should correctly resolve and fetch PR refs for fork-based Bitbucket PRs and allow the pipeline to execute successfully. -Fork-based PRs trigger CI pipelines reliably. -Harness correctly resolves Bitbucket fork PR references and checks out the PR source code. -PR metadata (fork repo, source branch, commit SHA, target branch) is made available to the pipeline. -Pipeline execution does not fail due to PR ref resolution errors. -Behavior is consistent with PRs originating from the same repository.

This is a feature request for project resource groups. Currently you can only restrict a resource group to either all input sets or specific input sets by identifier. Would be good if there was a way to restrict the resource group to input sets based on their pipeline identifier (all input sets for a specific pipeline). Unless this is already a restriction inherited from the resource group's pipeline restriction.

I have a harness pipeline where I need to send email after pipeline steps are completed. The pipeline is used to run automation tests and lastly I need to send a report over email. However, I do not have SMTP username and password set at organisation level. Could you help me in creating the SMTP service account with username and password? Pipeline: https://globalpayments-sbx.harness.io/ng/account/MTEyYzc0MTctMzIyYi00ZT/module/cd/orgs/rtr/projects/rtr_automation_pipelines/pipelines/rtr_automation_ui/pipeline-studio/?storeType=INLINE

Request native Orka integration for macOS VM build infrastructure in Harness CI. Customers using Orka cannot leverage Harness CI for macOS builds today (as opposed to customers using Anka). Please add first-class Orka support, including: Orka-based macOS VM provisioning Integration with CI pipelines (similar to Anka) Basic setup documentation

Add support for node/npm to build intelligence