I’m attempting to configure Azure DevOps pipelines for continuous integration (CI) but when I commit a change into a specified target branch and push it to the remote origin (other Git) it is failing to trigger the pipeline build.
According to https://docs.microsoft.com/en-us/azure/devops/pipelines/build/triggers, it's possible to select the pipeline CI triggers even if your source code is in a remote Git repo or Subversion because when using this trigger, it will mean that azure pipelines polls for changes at a regular interval.
Based on this information below is how i configured the CI trigger in Azure Devops
Bitbucket is our Git repository management solution which is self-hosted (not cloud), it is available on a public domain but requires authentication (username & password) to access the repository. As far as I am aware there is no firewall blocking the connection which I’ve read can block the connection.
In project settings in Azure Devops I have added a ‘new service connection’ of the type ‘other Git’ and specified the following settings (removed real values). With this service connection configured it is also configured to get sources.
If I trigger the pipeline build manually or set it to schedule there are no issues with it kicking off. I have tried playing around with different settings i.e. permissions it the portal but whatever I have tried I have not been able to push to the master branch and it trigger a build automatically.
Is this possible to achieve or am I missing something obvious? During my searching for a solution i have read about web hook, perhaps this is required?
Thanks
