Improve the triggering process with GitX
complete
S
Strong Pike
Today when you merge a PR, for example, that changes the pipeline configuration itself, the pipeline will trigger before the pipeline is synced with the new changes. Thus executing an old version and values for that pipeline.
For this enhancement, we want that first gitX files to be synced and then the trigger will act upon them.
Log In
Prasad Satam
marked this post as
complete
Hi everyone,
Thank you for raising this request and for the detailed feedback throughout this thread. We understand how disruptive it is when pipelines execute with stale configurations after a PR merge — especially in high-velocity environments with frequent pipeline changes.
This has been fixed. We've shipped an enhancement that ensures GitX files are fully synchronized before any trigger evaluates and fires a pipeline.
The execution order is now:
1. Webhook event is received (e.g., PR merge)
2. GitX syncs the latest pipeline YAML from your Git repository
3. The trigger evaluates against the updated configuration
4. The pipeline executes with the correct, up-to-date YAML
This means your pipelines will no longer run with outdated configurations after a merge. The workarounds of closing/reopening PRs or manually
re-running pipelines should no longer be necessary.
How to enable this:
This enhancement is controlled by the feature flag PIE_PROCESS_TRIGGER_SEQUENTIALLY. To enable it for your account:
1. Contact Harness Support and request that the feature flag PIE_PROCESS_TRIGGER_SEQUENTIALLY be enabled for your account
2. Once enabled, all webhook-triggered pipelines stored in Git (GitX) will automatically use the sequential sync behavior
3. No pipeline or trigger reconfiguration is needed on your side
For reference, here is the relevant documentation on configuring triggers with remote pipelines:
We'd encourage each of you who voted on this post to reach out to Harness Support to get the feature flag enabled for your accounts. Once you've tested it, we'd love to hear if this resolves your use case.
If this addresses your need, we'd appreciate it if you could mark this request as resolved. And as always, feel free to comment here if you have any
questions or run into issues.
Thank you for helping us improve the GitX experience!
F
Frequent Jay
This isn't just a feature request, this is a horrible bug and should be fixed ASAP.
Autopilot
Merged in a post:
Improve Git Synchronization Reliability
C
Cooing Rook
Problem Statement
Inconsistent Pipeline Behavior: When changes are made to pipeline configurations, the expectation is that these updates are immediately applied to the next pipeline run. However, due to Git synchronization issues, pipelines frequently run with outdated configurations. This inconsistency results in unexpected build outcomes, causing confusion and delays as developers attempt to troubleshoot problems that are actually due to stale configurations, not code errors.
Current Problems:
Git Sync Failures: The synchronization with Git is unreliable, causing pipeline configurations to not be consistently updated. This leads to pipelines executing with outdated settings and unexpected behaviors, which requires frequent manual intervention to correct.
Operational Impact: The synchronization issues are disrupting our development workflow, creating unnecessary delays and loss of productivity. This is especially problematic when rapid deployment of changes is needed, but the pipeline does not reflect the latest updates.
Manual Workarounds: To address synchronization issues, we are often forced to use manual workarounds, such as closing and reopening pull requests. This approach is inefficient and unsustainable for our fast-paced development environment.
Priority Level: P1 (Critical)
Impact: The Git synchronization issues are significantly affecting our development process by causing delays, reducing productivity, and increasing the risk of errors. A prompt resolution is critical to prevent further disruptions and ensure our CI/CD pipelines function as expected.
Prasad Satam
marked this post as
next fiscal quarter
Strong Pike- Thank you for submitting this feature request, we will prioritize this in our next Quarter and update this ticket with timeline and progress. Please feel free to add suggestions and questions to this thread.
L
Linen Pigeon
Prasad Satam/ Strong Pike We don't find any updates are progress here. Can you please share if this issue is fixed. We are still facing the issues
We had the issue ticket raised(#79322) in Feb 27th 2025 and its closed without any confirmation. Seems this is still not fixed