Folder/Directory support to segregate pipelines inside a project
long-term
I
Iron grey Chicken
We have all pipelines under single project only. I want ability to club together pipelines under a folder/directory which serve same purpose for better organisation and usability.
Creating different projects for each individual use-cases is not feasible.
Log In
V
Venetian yellow Caribou
Can this be prpritized, we have many teams additional projects for the sake of isolation
Canny AI
Merged in a post:
Pipeline Directories
C
Coral Kite
I would like a way to organize my pipelines better. A simple directory structure in the pipelines tab would work great.
Canny AI
Merged in a post:
Ability to Categorize the pipelines with Folders
V
Venetian yellow Caribou
Ability to Categorize the pipeline with Folders under Code Repos and CI CD pipelines, so that pipeline can clubbed into multiple folders giving the ability to segregate
Rohan Gupta
long-term
Rohan Gupta
Merged in a post:
Folders to structure pipeline view
F
Fluttering Koi
Folders to structure pipeline view
In Projects -> Pipelines
Is it possible to create folders to structure the project better ?
for example
./UI_Pipelines
./UI_Pipelines/Build.yaml
./UI_Pipelines/Test.yaml
./API_Pipelines
./API_Pipelines/Build.yaml
./API_Pipelines/Test.yaml
Just now all pipelines are just listed.
Rohan Gupta
Merged in a post:
organize pipelines in folders
B
Busy Guppy
organize pipelines in folders
I have many pipelines in my project, it would be nice to have a folder view to organize/hide some in the pipeline view
Rohan Gupta
Merged in a post:
Harness Pipeline and Secrets
I
Ink Trout
Hi Team,
Based on suggestions from our colleagues, we would like to request two features that are either currently unavailable in Harness or of which we are not aware:
The absence of grouping/folder structure for secrets in Harness requires us to place secrets associated with a particular service in one folder. Consequently, we need to grant access to that folder only to the concerned individuals responsible for that service.
Similarly, for pipelines, we require grouping functionality. When there are multiple sub-services under one main service, each having its own pipelines, we need the ability to organize these pipelines under a common folder. By doing so, we can restrict access to that folder only to the relevant personnel for that specific service.
For example, consider "axiom-prime-core-services" with the following sub-services:
I. current-policy
II. current-submission
Each of these sub-services has its own pipeline. We would like to create a folder named "axiom-prime-core-services" in Harness pipelines, place the pipelines associated with these sub-services under that folder, and then grant access to this folder only to the concerned individuals.
Prasad Satam
pending feedback
I
Iron grey Chicken
Prasad, please confirm if we have ability to filter pipelines using tags and executing it at runtime?
Ask is not for humans but automation, as we would need to have multiple versions of single pipeline in same project. eventually it would provide more confidence to users because they can easily differentiate same name jobs using different paths which would not be possible using Tags.
Use case is to identify pipeline to be executed at runtime depending on input provided, please let me know if there is any other alternate solution
Prasad Satam
Hello Vishwa, Thanks for creating this feature request. Can you I point you in the direction of tags for better organization - https://developer.harness.io/docs/platform/references/tags-reference/. We can add tags to the Pipelines and then search for them through the filter.
Load More
→