If you're working out of an Azure repository, there's a chance you may have had some difficulty getting a CI job to work due to some additional steps involved during setup. Fortunately, we have two quick tips that should have you automating your deployments in no time: Correctly authenticating your repository and ensuring proper settings of your webhook.
Azure Repo Authentication:
In order to connect your Azure repo, navigate the master branch and click "Clone".
After clicking clone, you'll need to take the URL that is generated and remove the "username@" section, as shown below.
Once you've removed the "username@" section, copy the URL and paste it into the Git Repo URL field of your Azure DevOps org in Copado Essentials.
After you've connected your repository, you're all set to setup a CI job using a webhook.
Azure Repo Webhook Setup:
Once you navigate to the CI Jobs tab, click New CI Job, and setup the job for whatever action you need to occur. To have the CI Job initiated by a webhook, leave the Schedule field set to "None", select "Triggered by git commit to branch", then click on the "Setup Webhook" link to open the details pop up screen.
In the pop up details, copy the URL. This will be used in the Azure settings page later.
Now, log into your Azure DevOps and click the corresponding Project, open the Projects Settings page, then select Service hooks, Web Hooks, and "Next".
In the next page, select "Code pushed" for Trigger on this type event and the Git repository you want to trigger this webhook. Leave all remaining fields on the "Any" option.
In the Action pop up screen, copy and paste the URL from Copado Essentials into the URL field. Click on Finish, then navigate back to Essentials for the final step.
Within the CI Job you've been editing, click Save, then navigate to the "Deploy Options" subtab within your CI Job. Next, you'll choose the option under "Git source" that states "deploy files committed since last successful build", then choose the most recent build on from the list.
Once you click Save, your CI Job will be triggered by any merge to the branch specified as your source org!