Feature Requests

We are currently using a curl to upload to nexus, it would be great to have a built in step to do this for us.

User need the ability to use the cache on a stage but only upload in 1. This will allow us to save 1 minute in total execution time, and many more minutes in execution minutes. Turning off only the uploading of cache on a per stage basis would solve the issue for them.

Early new year App Store will stop accepting apps build on previous SDKs as IOS sdk 18 has been released on September 16,2024. Currently, Harness supports Xcode 15 on IOS sdk 17 as per following documentation: https://github.com/wings-software/harness-docs/blob/main/harness-cloud/macos-14-Readme.md

Ability to use Docker build secrets. Add the option to specify secrets against the built in Build and Push mechanisms.

I would like to see stage information like status, name, type and error summary. This will help us to measure tests and executions in CI, but also help measure the pipeline's stages that will give visibility to dev and devops teams, that will allow them improve stages that are not performing as expected. Like the image I attached, but for CI stages on repository data source.

Currently Harness publishes to GCR but not to AWS's public ECR. Harness should also publish the images to ECR since i'm certain most users leverage AWS for their builds and deploys. Getting rate limited on Dockerhub is a pain.

I want upgrade the plan to execute my operations through the pipeline CICD.

Hello all. I need edit access on pipelines because pipelines created in LSE cannot be run here (some params are missing). Please enable edit access on pipeline for me. I am a comp owner and this hinders my ability to create proper pipelines for my comp.

Would like to create dashboards based on what infrastructure each Build stage is using. This way I can see how much each VM pool or K8s cluster is being used across the account, sliced by org, project and pipeline. Would help with usage metrics, capacity planning and other SRE decisions. For example: Project A used 200 minutes of K8S cluster Y and 50 minutes of VM pool Z for builds last week.

We would like the ability to hide or restrict unapproved plugins from being used in steps. Harness admins should have the capability to disable certain plugins to prevent their usage. For example, developers currently use Kaniko for building images, but we want to block this to ensure compliance with our internal policies.