H
Honey Kingfisher
I’m working on a mono repo setup and have encountered a couple of limitations in Harness that I’d like to propose as feature enhancements:
  1. Multiple Triggers per Pipeline in Mono Repo
Currently, it seems Harness does not support defining multiple Git triggers within a single pipeline that can respond to changes in different folders or branches. This is a common pattern in mono repos where services are organized by directory, and each service may need its own trigger logic.
Feature Request:
Enable support for multiple Git triggers per pipeline, with the ability to:
Scope triggers to specific folders or file paths.
Define branch-specific behavior.
Use matrix strategies to run pipelines for multiple changed directories.
  1. Jenkins-Style Branch Discovery Strategy
In Jenkins, the branch discovery strategy allows users to:
Discover all branches.
Discover only PRs.
Discover all branches except PRs.
This is particularly useful to avoid duplicate builds for PRs and their source branches, while still building key branches like main or develop.
Feature Request:
Introduce a branch discovery strategy in Harness similar to Jenkins, with options to:
Discover all branches.
Exclude PR branches from discovery.
Include exceptions for specific branches.
These enhancements would significantly improve Harness’s usability for mono repo workflows and align it more closely with established CI/CD patterns.
Thanks for your time and support!