Segregation of pipelines
under review
E
Effective Unicorn
Segregation of CI and CD pipelines for easy maintenance and better readability. Folder structure for maintaining CI and CD pipelines based on services or tech stack.
Log In
Canny AI
Merged in a post:
Segregation of pipelines based on CI and CD
E
Effective Unicorn
All pipelines are messed up, i can see CI pipeline in CD and CD pipeline in CI. Need this enhancement to segregate based on CI and CD pipeline.
Sudarshan Purohit
Could you add more details around the problem you're facing, Effective Unicorn? We display CI and CD pipelines in the CI and CD sections of the nav today, and these are classified based on whether they have CI and CD stages in them, respectively. A pipeline that has both kinds of stages will show up in both sections (by design).
Besides these, we support creation of filters in the Pipeline Executions list based on which service was deployed, or if the separation is team-wise, separate projects could be used to separate the pipelines.
E
Effective Unicorn
Sudarshan Purohit can you please elaborate and make me understand on how to use filters for segregation of pipelines based on team or any other category?
Sudarshan Purohit
Effective Unicorn Filters can be created and saved, then used to view only the required pipelines or executions (https://developer.harness.io/docs/continuous-delivery/x-platform-cd-features/executions/execution-history/#filter-executions). In case specific custom attributes are to be filtered on, we recommend using tags.
If the teams pipelines are completely segregated from each other we would recommend using separate projects for them.
Shylaja Sundararajan
under review