harness - The Modern Software Delivery Platform®
Create
Log in
Home
Feedback
Feature Requests
Log in to your harness - The Modern Software Delivery Platform® account to give feedback
Log In
Boards
Feature Requests
Powered by Canny
Feature Requests
Anonymous
Feature Requests for Harness. Select 'Category' based on the module you are requesting the feature for.
Details
Category
Continuous Delivery & GitOps
Continuous Integration
Feature Flags
Cloud Cost Management
Service Reliability Management
Security Testing Orchestration
Chaos Engineering
Software Engineering Insights
General Platform Requests
Internal Developer Portal
Code Repository
IACM
Continuous Error Tracking
Drone 2.x
Open Source
SSCA
Database DevOps
Uncategorized
Showing
Trending
Sort
Trending
Top
New
Filter
Under Review
Planned
In Progress
This Fiscal Quarter
Next Fiscal Quarter
Long-term
Pending Feedback
Complete
posts in
All Categories
All Categories
Continuous Delivery & GitOps (1,375)
Continuous Integration (294)
Feature Flags (72)
Cloud Cost Management (176)
Service Reliability Management (8)
Security Testing Orchestration (71)
Chaos Engineering (26)
Software Engineering Insights (87)
General Platform Requests (360)
Internal Developer Portal (60)
Code Repository (35)
IACM (14)
Continuous Error Tracking (11)
Drone 2.x (11)
Open Source (30)
SSCA (4)
Database DevOps (6)
Upgrade MacOS image Xcode 16.3 for CI builds
Upgrade MacOS image Xcode 16.3 for CI builds
0
2
Automatically retry failed git clone operations
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!
1
·
under review
1
Docker Delegate to run on a server as nonroot user
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
1
·
under review
0
queue build jobs at Org & Project level in addition to Account level.
Coming from jenkins, we had the ability to queue certain jobs. We want the ability to queue jobs more efficiently at the Org and Project level.
1
·
pending feedback
2
Support for MODULE.bazel in Cache Intelligence
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
1
·
under review
1
TI for Javascript/Typescript
User wanted have the support of Test Intelligence for Javascript/Typescript.
3
·
in progress
8
Add support for HTML Artifacts/Reports
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
26
·
long-term
34
Github Actions available for VM Infrastructure
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.
1
·
under review
2
Ability to view the full step logs
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
11
·
long-term
29
prevent leaking GitHub tokens on failed actions
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.
1
·
under review
1
Load More
→
Powered by Canny