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
We're using an argocd notification trigger based on the last reconciliation time to make a callback to an Azure pipeline. This way we can trigger a notification/callback by refreshing the application.
Our pipeline job is getting falsely canceled by the following notification, because the is_finished boolean evaluates to true when phase is "<no value>". But in reality the sync is not yet finished and now the wait step has failed for no reason. I'm not sure why phase is being set to "<no value>" and mostly it doesn't happen and the pipeline runs as it should. The pipeline basically patches the pull request properties and waits, and then it calls the argocd api to refresh the application, which should trigger a notification in case there is no change in the health status or phase status.
Hi,
We're using an argocd notification trigger based on the last reconciliation time to make a callback to an Azure pipeline. This way we can trigger a notification/callback by refreshing the application.
Our pipeline job is getting falsely canceled by the following notification, because the is_finished boolean evaluates to true when phase is "<no value>". But in reality the sync is not yet finished and now the wait step has failed for no reason. I'm not sure why phase is being set to "<no value>" and mostly it doesn't happen and the pipeline runs as it should. The pipeline basically patches the pull request properties and waits, and then it calls the argocd api to refresh the application, which should trigger a notification in case there is no change in the health status or phase status.
Here is the notifications configmap I used:
The text was updated successfully, but these errors were encountered: