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
When disablePolling is enabled in a Git repository, Fleet fetches the latest commit but does not apply it to the deployment. The same behavior is observed with Azure DevOps.
Expected Behavior
when disablePolling set in gitrepo, New commits from webhook should trigger deployments
Tested in with Rancher v2.9-5e27c2a5f9a245cad28ba209988eb7efb6b80447-head and fleet:104.1.1+up0.10.5-rc.1 deployed in GCP and working:
Steps done:
Created Github webhook with SSL verification disabled and Payload URL with https
Deployed above mentioned rancher version with 3 ds clusters. Passed as ingress reverse order of GCP ip with nip.io. Detailed steps here: Configure Github Webhook and Fleet
Backport of #2969
Is there an existing issue for this?
Current Behavior
When disablePolling is enabled in a Git repository, Fleet fetches the latest commit but does not apply it to the deployment. The same behavior is observed with Azure DevOps.
Expected Behavior
when disablePolling set in gitrepo, New commits from webhook should trigger deployments
Steps To Reproduce
simple
path and setdisablePolling: true
Environment
Logs
The text was updated successfully, but these errors were encountered: