Feature Requests

We would like to be able to update the next sequence id for a pipeline. We use the sequence id to version artifacts i.e. 1.0.0-<+pipeline.sequenceId>. Artifact version collisions will happen when migrating from jenkins, deleting and recreating a pipeline, moving a pipeline to another project.

please enable ff CDS_MARK_PIPELINE_AS_FAILURE

Pipeline execution metadata, including inputset used, version of pipeline used, maybe a summary of some sort of templates used if templates exist, what versions those templates are on so on.. Just a single place to see what was ran and what version. I see inputset details are enabled: Feature Request: https://ideas.harness.io/feature-request/p/show-input-sets-used-in-pipeline-executions-page Harnes Docs: https://developer.harness.io/docs/platform/pipelines/input-sets/#view-and-filter-executions-by-input-set FF to enable: CDS_EXECUTION_LIST_CARD_VIEW – Enables the new execution page UI. PIPE_ENABLE_INPUT_SET_FILTER – Enables input set-based filtering in the execution list. but like input set, there are other details that would help, again like the version of the pipeline that is being ran if its a template, as well including additional details of other templates used if any. But mainly this ask is about pipeline version being ran, and adding any additional details as well... Thanks! Keep up the amazing work Harness team!

Users should have the ability to configure notification rules in order to receive the desired build status updates. I have attached references from teamcity user profile.

Hi Team, Could you help in configuring emails in the pipeline so that developers receive email alerts for Harness approval gates? We already have pipeline failure notifications in place. This request is to ensure developers also receive email alerts for Harness approval gates, so they don’t miss any approvals when running pipelines from a GitOps perspective. Regards, Jerin

Currently the steps for helm deployments are limited to deploy/rollback/delete etc and the helm commands are included part of these steps. However, Having a separate step that has configurable helm commands would give more control and help leverage the helm features.

The App-of-Apps pattern is widely adopted in ArgoCD to orchestrate applications across environments and clusters. We require the ability to define a root “App-of-Apps” in Git that can manage child applications targeting different clusters and namespaces. Currently, Harness GitOps does not support this pattern natively for multi-cluster use cases. Requested Capability: Native support in Harness GitOps for multi-cluster deployments in the App-of-Apps pattern.

We need the ability to : To run some number of pipelines in parallel at a time and keep other in queue, this is not possible with queue and barrier step. How to throttle the number of maximum parallel pipeline executions? How can I indicate the max Concurrent of pipelines? And the other stay in queue.

Please add the ability to use kustomize

Make org-scoped environments discoverable in Environment Tab(currently project-level environment) views to reduce friction and improve developer UX.