Why doesn't Azure Pipelines pick up commit on GitHub?

Question

We use Azure Pipelines for our CI/CD processes since a few weeks. The CI pipeline gets code from GitHub, builds, tests and creates a deploy package.

From the beginning I am quite certain that every commit got detected as intended, but recently that is not the case. Manual triggers and scheduled triggers work, but continuous integration does not.

What could be the causes for this?

In the pipeline, we checked the box for "continuous integration", and we use the recommended GitHup App to provide authorization. This is verified to work, we can see the authorized GitHub repos in the pipelines settings.

Answer 1

We ended up changing how we connect from Azure Pipelines to GitHub. The recommended way is to install the Azure App in GitHub and connect using that in Pipelines. My experience is that it worked at first, but stopped working. I read somewhere that only the first connection works with webhooks, so maybe we tried it somewhere else or something that broke it. I ended up using a GitHub servic account to pull and listen for webhooks, and that works just as expected.

Answer 2

You can check if the github branch you committed to is included in the Branch filters. If it is not included. Click Add to add the branch.

Check if there is skip CI command(eg.[skip ci]) in commit message. See here for more information.

If CI trigger is not working even all the settings are correct. You can try below workarounds:

1,Disable the CI trigger, save, then re-enable it and save it again.

2,Clone your build definition. See below screenshot

3, Create a new build pipeline with the same trigger and settings.

If all above arenot working. You can go to this site to see if there is a server outage of azure devops.