GitX Support for Feature Branches in CV Step
under review
B
Beryl Mandrill
Impact: High, affects onboarding and long-term scalability of GitX usage in CD pipelines
Background:
While executing pipelines from feature branches using GitX, the CV step fails to display verification results. Although the step technically runs (i.e., verification is performed), attempting to view the results triggers a 500 Internal Server Error.
Root Cause (as identified by Engineering):
The CV step currently only fetches service and environment definitions from the default branch. Feature branches are not supported for monitored services used in the CV step, which causes a disconnect when executing pipelines from non-default branches.
This behavior was confirmed as expected and documented after internal investigation:
- Monitored Services: https://developer.harness.io/docs/platform/monitored-service/
- Verify Deployments: https://developer.harness.io/docs/continuous-delivery/verify/configure-cv/verify-deployments/#step-4-create-a-monitored-service
Feature Request:
Enable GitX support for feature branches in the Continuous Verification step, so that:
- Service and environment definitions can be fetched from the feature branch.
- Verification results display correctly when executing from a non-default branch.
- Users are not forced to merge changes into the default branch just to verify changes.
Log In
Shylaja Sundararajan
under review