Improve the triggering process with GitX
next fiscal quarter
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
Canny AI
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
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.