Support webhook with ArgoCD？？？？？

[Brook Hans]

Description of the situation where bitbucket webhook does not trigger argocd:
The status code returned by bitbucket webhook is 200, and argocd can receive the push event normally without reporting an error, but it cannot trigger refresh. Tried the following, but still doesn't work:

1. Modify bitbucket, argocd and other configurations
2. Test and deploy HA version and non-HA version
3. Change argocd version (lower version)
4. Change bitbucket address
5. Troubleshoot network problems (in your own cloud account environment, release all network restrictions, deploy argocd and test)
6. Replace the gitlab code base for comparative testing
   Comparison found that gitlab returned logs
   time="2024-01-08T02:54:43Z" level=info msg="Received push event repo: http://xxx/root/test-deploy, revision: main, touchedHead: true"
   time="2024-01-08T02:54:43Z" level=info msg="Requested app 'gitlab' refresh"
   bitbucket returns log:
   time="2024-01-08T03:11:51Z" level=info msg="Received push event repo: https://bitbucket.org/xxx/xxx, revision: master, touchedHead: true"
   Compared with cashback, gitlab first receives a push event and then refreshes it to refresh normally. Bitbucket only receives push events, no refresh, and cannot be refreshed.

[Theodora Boudale]

Hi and welcome to the community!

I'm not sure what you are referring to by "Bitbucket only receives push events, no refresh". If you have a webhook set up to trigger on push, then every time commits are pushed to the repo, Bitbucket will send a request to the URL configured on the webhook settings.

If by 'refresh' you mean something that you expect to happen on Bitbucket Cloud side, can you please explain what exactly is the Bitbucket event/action you are referring to?

If by 'refresh' you mean ArgoCD refreshing something after receiving the webhook payload, I would suggest reaching out to ArgoCD's support team for help with troubleshooting.

Kind regards,
Theodora

[Brook Hans]

Hi, Thanks a lot for your comment,
It should be ArgoCD‘s refresh action, ’
Refresh: Fetches the latest manifests from git and compares diff.
I wish bitbucket cloud can communication with ArgoCD community to check on this ?
if not support yet, work with ArgoCD community to make it work.

[Theodora Boudale]

Hi,

Thank you for the clarification.

Bitbucket Cloud has no control over what happens on the destination server once the webhook payload has been received. If nothing is triggered at all, I would suggest reaching out to ArgoCD community or support team for further steps with troubleshooting, as this is outside the scope of our support.

If ArgoCD attempts to do a refresh (which I assume may be a git pull or git fetch from a Bitbucket Cloud repo) and that fails e.g. with an authentication error, we can guide you to ensure that the correct credentials are used. But if nothing is triggered at all, then the ArgoCD team will be better equipped to help.

Kind regards,
Theodora