Forum Discussion
GitHub App authentication for Azure Pipelines causes webhooks to dissapear
Greetings,
we are using GitHub as the code repository service together with Azure DevOps Pipelines for CI/CD.
- All the pipelines need to have their triggers authenticated to GitHub in order for the pipelines to trigger
- Authentication works either with personal OAuth Service Connections or via the Azure Pipelines App for GitHub
- The recommended way is using the Pipelines App
The problem: when I authenticate the pipeline trigger via the GitHub Azure Pipelines App, the webhooks from the repository which the pipeline is pointing to dissapear and the automatic triggering stops working!
To make the issue even more ridiculous - we have 5 pipelines but only with 4 of them this happens! One is working completely fine with with the recommended GitHub App authentication.
What I tried:
- Recreating service connections in Azure DevOps
- Reinstalling the Azure Pipelines GitHub App
- Recreating the pipelines
Nothing worked, I am forced to use OAuth which is always throwing a warning to switch to app authentication because it's better performing and more reliable.
Quite ridiculous to recommend a certain way of doing things, then making it work less reliable than the not-recommended way.
Anyone has any ideas? Thanks in advance.
1 Reply
I've seen the same thing.. "
This pipeline is using an OAuth-based connection. Switch to the Azure Pipelines GitHub App for improved reliability and performance."
If I switch it removes all the webhooks. Then the checks seem to get stuck in Pending state on PRs.
It seems more reliable to use the oAuth connection and the webhooks!
Amazing this has gone years with no comments..
