You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
The deployment pipeline currently fails with the error: Unable to resolve 'build/NaN' to a commit SHA.
This happens when trying to deploy multiple components (e.g., 10) in one run. The issue arises because the ApplicationSet resource is patched, but the Argo CD Application controller does not update all Application resources instantly. As a result, some Applications are left in an inconsistent state, causing synchronization errors.
Describe the solution you'd like
The deployment pipeline should include a mechanism to ensure that all Application resources are fully updated before proceeding with synchronization.
Describe alternatives you've considered
Adding a fixed delay (sleep command) after patching the ApplicationSet resource.
Additional context
This issue becomes more apparent when deploying a large number of components simultaneously. For example, in a pipeline with 10 components, the error consistently occurs but is resolved if the pipeline is re-run after a short delay.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
The deployment pipeline currently fails with the error:
Unable to resolve 'build/NaN' to a commit SHA
.This happens when trying to deploy multiple components (e.g., 10) in one run. The issue arises because the
ApplicationSet
resource is patched, but the Argo CD Application controller does not update allApplication
resources instantly. As a result, some Applications are left in an inconsistent state, causing synchronization errors.Describe the solution you'd like
The deployment pipeline should include a mechanism to ensure that all Application resources are fully updated before proceeding with synchronization.
Describe alternatives you've considered
Adding a fixed delay (
sleep
command) after patching the ApplicationSet resource.Additional context
This issue becomes more apparent when deploying a large number of components simultaneously. For example, in a pipeline with 10 components, the error consistently occurs but is resolved if the pipeline is re-run after a short delay.
The text was updated successfully, but these errors were encountered: